ToyboxCreations SELECT * FROM [My Life]

RIP Microsoft SQL Server 2000

SQL Server 2000 will comes out of Mainstream support today!

What this means is that SQL Server 2000 will still be the subject of security fixes, and you can still get paid support for it, but other fixes will only be available if you take out extended support, which you have to pay for.  If you weren’t aware of this, then I can suggest you look to migrate as soon as possible and in the meantime consider taking out extended support if your database is mission critical. Or if other companies depend on your Database servers.

If you have servers still running SQL 2000, you can use upgrade adviser to check for any changes you'll have to complete before upgrading your SQL 2000 instances to 2005/8.

You can also check out the TechNet Forums and see what issues others have had in their conversions and how they were resolved.  This is the second best option for migrating to a newer instance of SQL Server.  The best is to work with a Database Engineer (did I mention I'm a Database Engineer?) or Microsoft Support directly to migrate your systems to a newer version of SQL Server.

If you absolutely must have a SQL Server 2000 instance to run your system, may I suggest trying to run a newer version of SQL Server in compatibility mode.  This allows an instance of SQL Server 2005/8 to effectively emulate the functionality of SQL 2000.  This is a band-aid at best.

In closing, I would like to express my concern to if you continue using SQL Server 2000 after today without purchasing extended support, or begin your migration to a later version of SQL Server.

Related posts:

1. sql server 2000 + How to display date time
2. Introducing Microsoft SQL Server 2008 R2 eBook
3. SQL Session – Fast Times at SQL Server High
4. Microsoft Continues to Support PHP
5. SQL Session – Inside SQL Server Policy-Based Management

About Shannon Lowder

Shannon Lowder is the Database Engineer you've been looking for! Look no further for expertise in: Business Analysis to gather the business requirements for the database; Database Architecting to design the logical design of the database; Database Development to actually build the objects needed by the business logic; finally, Database Administration to keep the database running in top form, and making sure there is a disaster recovery plan.