We will be performing major upgrades on MSSQL5 and MSSQL7 from SQL 2000 to MSSQL 2008. As part of these upgrades we will have an extended maintenance period each night from 11pm Central, until 6am Central starting at 11pm Central on Nov 4th. SQL services may be unavailable during these times.
We will followup these upgrades to 2008 with additional servers need updated on the following weekends, further notices will be provided for their scheduled updates.
Re: MSSQL5 and MSSQL7 upgrade to SQL 2008, Nov 4/5/6
Services on MSSQL7 are currently still running. I went for a couple Windows updates first, and allowing it to be up as much as possible. It will however be going down for updates at any time in the next 15 minutes.
Re: MSSQL5upgrade to SQL 2008, Nov 5/6 11PM - MSSQL7 - Completed
MSSQL5 windows updates going, services will remain up until reboot time, and we will update a few minutes before that, but expect in the next 20 min to 50 minutes
Re: MSSQL5upgrade to SQL 2008, Nov 5/6 11PM - MSSQL7 - Completed
It is a bug in SQL 2008 that is fixed in 2008 SP1, but never encountered by us before, we are trying to see what process is needed to fix it at the state it is in now.
Re: MSSQL5upgrade to SQL 2008, Nov 5/6 11PM - MSSQL7 - Completed
We have hit a snag where if the ‘sa’ account is renamed, SQL service fails to start, it is fixed in SP1 but you have to have a slipstreamed installer to have that work, since we never encountered this error we had not done that process. We will be making that before the next series of upgrades, for the time being we are trying some workarounds.
Re: MSSQL5upgrade to SQL 2008, Nov 5/6 11PM - MSSQL7 - Completed
We are working to resolve this, and not do a rollback, a rollback is going to be time consuming, and also will make the entire process have to start again in the future, so we’d prefer to get it resolved completely now.
Re: MSSQL5upgrade to SQL 2008, Nov 5/6 11PM - MSSQL7 - Completed
We are trying a repair install as we’ve dug deep into the stored procedure that is failing and it is something that did not even exist in 2000, so it is not an upgrade related failure exactly, is the the data collection user permissions and settings that look to have failed.