Well it isn't likely to cause quite the same stir as Y2K but I thought it was a significant date for everyone's diaries...
On the 8th April 2008 Microsoft withdraws mainstream support for SQL Server 2000. Look here if you don't believe me. That's not very far away at all.
This gives everyone who is currently using SQL 2000 just over a year (and possibly only one budget forecast / round) to migrate to the new platform unless you wish to pay for extended support from the mighty M$.
In my experience people can get quite blasé about support from Microsoft and have been known to adopt a "who cares" attitude. To some extent I can understand that; after all when was the last time you had to phone them up for support? However, this is SQL Server we are talking about - that means data. If and when you have a problem accessing your data I know I wouldn't want to be the DBA turning round to the board or CTO explaining that we have an unsupported platform holding all the company data. I think it's fair to say that if you have read this you have now been forewarned...
There is one question still in my mind about upgrades though and that is; what support is there for SQL 2000 DTS packages that have been imported into SQL 2005?
Recently I ran the SQL 2005 Upgrade Advisor on a clients database server as I was looking for issues with their DTS packages.
There was one message there that raised some concerns especially when thinking about the imminent end of mainstream support. It said:
SQL Server 2000 Data Transformation Services
Advisory
SQL Server 2000 Data Transformation Services is deprecated You must completely migrate existing SQL Server 2000 Data Transformation Services (DTS) packages to SQL Server 2005 Integration Services packages before support is withdrawn.
Source Type: MSDB Package
From this message it would imply that importing legacy DTS packages into SQL Server 2005 will not be sufficient for you to keep receiving ongoing support. It quite clearly states that the package must be migrated. It also raises important considerations regarding on-going support in Katmai. Will the downloadable DTS designer still be available? What will the suppport be for the Execute DTS 2000 task? There's a lot of questions out there. For the official word from M$ on backward compatability click here. To me though, the answer is this:
It's time to get a wriggle on - especially if you have a large number of SQL 2000 instances. It will require investment, both in terms of time and money but also people and process; so my advice would be start planning, budgeting and learning! These kinds of upgrades don't happen over-night. The regression testing alone can be a very intensive process. As we all know, upgrades are a lot of work! My one piece of advice to you here is to ensure that you have identified and agreed the acceptance test criteria for a successful upgrade before you perform the upgrade. This, I think, is the key step in the upgrade process:- define success.
There is also some good news. Microsoft have provided the SQL 2005 Upgrade Advisor to help you identify issues with your installations. Additionally, DTS packages don't have to be migrated straight away. You can just import them and execute them as is. There is also a package migration wizard to help you perform your migration although I personally prefer a more holistic approach (see below). Furthermore, SQL Server 2005 Service pack 2 is also just around the corner which will mean your migration should have a very stable target platform to migrate to.
To fully leverage SSIS and make the most of the platform will require careful consideration. Things you did in DTS you can and would do differently in SSIS. It's quite a steep learning curve but there are some great resources out there for SSIS notably sqlis and of course this site. My advice would be to take the time to really understand how this platform works and what it can do for you before implementing your own migration of DTS to SSIS. To me there is little point in upgrading technology without looking to use the new features and ways of working. Just make sure you have a plan to do it before your support from Microsoft expires...
So the question to ask yourself is this "Is now the time to be (finally) moving to SQL Server 2005?"