With SQL 2000 End of life nearing on April 9th, just 22 short days away, I was wondering who still has SQL 2000 in production. I for one have several instances active and in production with SQL 2000. All are third party applications that based on the version of the app we have installed does not support SQL 2005 or above. All of my SQL 2000 instances have a plan in place to be upgraded and or replaced within the next 6 months but I will still be past the point of support which makes me feel uncomfortable. Who else is in a similar situation and what are you planning to do to mitigate your risk such as only running it in a VM with a clone of the OS, or exception out the server from patching to eliminate risk of a change breaking it?
I have a couple of customers that are stuck with SQL 2000 instances for business reasons. So our approach is: 1. Virtualize all the servers so that the hardware aspect is covered. 2. Create a up to date clone of the server/os. 3. Make sure that all dependencies for the databases/system are scripted or documented. 4. Create a recovery plan per database/system for the virtualized server/clone. 5. A "no touch" policy for the server, only patch if really necessary. 6. Charge the departments that "own" these databases/server appropriately for the "special treatment".
*wave* Yup, I still have SQL2000 in production - SP3a and SP4. The joys of looking after legacy systems. What we're doing, though, is mothballing systems after migrating data out into the newish parent company.
Moved as much as we could to SQL Server 2005/2008 and ran in compatibility mode which was fine for some applications such as Dynamics GP, FileNet or thick client VB apps. However other applications such as BizTalk, SharePoint or Dynamics CRM were not so we had to move 2000 eventually.