November 10, 2009 at 8:19 pm
Not sure if this is the right area/thread/forum but...
We currently operate a database that is just over 1Tb and uses SQL 2000.
I would like to undertake an upgrade program to go to either SQL 2005 or (preferably) 2008.
Owing to a small global financial thingy currently going on, my boss wants a business case written around the risks of running a database on SQL 2000 and how we can mitigate this going to 2005/2008. No problem I say, there are lots of issues around SQL 2000 (I did have my fingers crossed behind my back whenI said that).
So my help/question/plea/etc is for anyone who can think of reasons/problems (known or hinted at)/issues that I can put in that lead one to logically conclude that it is worth going to 2005 or 2008.
Many Thanks
John
November 11, 2009 at 2:49 pm
Well I would say that your biggest selling point would be that Microsoft dropped support for SQL 2000 last year. There is still extended support until 2013, but that is mainly just security patches, not fixes against the database engine itself. Your company may be able to get support through premier support, but that is going to be very costly per call.
Other than that there are plenty of reasons I would think you would beneifit going to either version. SQL 2005 brought in CLR, much better management plans and SSIS over DTS, way better reporting support, and things like backup checksums, which can alert one sooner to corrupt data.
2008 goes even further with things like backup compression, filestream data types, geospatial support and many other features.
I would take a look at Microsoft's site for differences between the versions to help make your case.
Joie Andrew
"Since 1982"
November 11, 2009 at 3:14 pm
Some other features which are not mentioned, such as Resource Governor, Policy Based Management, Change Data Capture, Transparent Data Encryption, Database Partitioning, HA feature DB Mirroring and Peer-to-Peer Replication and many more things to look for.
Look at all of them and come up with those features that really makes a best case in your situation.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 16, 2009 at 11:04 pm
Keep in mind flashy new features that you don't need or are unlikely to use don't sell it. the fact that SQL 2000 is end-of-life and that you can't get db engine fixes without $$$ means what you have is what you get and not all security fixes will be make available. Also SQL 2005/2008 are much better able to handle 1TB of data than SQL 2000. Compressed backups in SQL 2008 Enterprise edition come to mind with that much data.
CEWII
November 17, 2009 at 1:13 am
unixbomer (11/11/2009)
Well I would say that your biggest selling point would be that Microsoft dropped support for SQL 2000 last year. There is still extended support until 2013, but that is mainly just security patches, not fixes against the database engine itself.
To take advantage of extended support, a company must already be a premier client and must be paying extra for extended support.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 17, 2009 at 7:00 am
Excellent point, so basically you don't even have that option..
CEWII
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply