SQL 2K5 vs SQL 2K8?

[wbodger]

So, I am to the point where I believe I can finally update our CMS from SQL2K to SQL 2K5(or perhaps SQL 2K8?). My question is how different are 2K5 and 2K8? If I am coming strictly from a SQL 2K environment, is there really much difference between 2K5 and 2K8 as far as learning curves? Next, what about compatibilities? I know that, for instance, I have to re-do my DTS packages for 2K5 , right (into SSIS)? Can I really even go from SQL 2K to SQL 2K8? Is it better to detach a database from a 2K machine and then attach it to a clean 2K5 or 2K8 machine, or is it better to follow an in-place upgrade path?

Thanks fr you help!

Willie

 

[djj55]

There are several things to watch for when upgrading from 2k to 2k5 or 2k8. Not the least is the deprecated items (sp_sendmail and sp_makewebtask are two). We went with 2k8 because it has a longer support "life".

Depending on your situation as to the upgrade path to take. Google and you will see white papers on this.

Sorry I can not be of more help but it was not a painful upgrade.

Good luck,

djj
The Lord is my shepherd (Psalm 23) - I need someone to lead me!

 

[ousoonerjoe]

Our shift from 2k5 to 2k8 and then on to 2k8r2 had trouble on the upgrades (mostly self-induced), but the performance and "add ons" were well worth the fight. The Change Data Capture (CDC) alone has been an immense tool in auditing and in some places, trouble shooting stored procedure inserts and updates. They both support "Legacy DTS" processes, though how much and for how long will require a Google search.

With each upgrade (as mentioned above) we simply detached and reattached each database after the upgrades completed. There were no complications at all with this (we did make backups just in case though).

As djj55 mentions, the longer duration of support also adds to the reasons to go ahead and at least move to 2k8 if not r2. If my memory serves me correctly, the 2k8 and r2 upgrades had tool sets for upgrading from 2000 directly (again, Google is your friend in verifying this).

While I'm a fan of Oracle, being an acting DBA in MS-SQL for the last few years and working with 2k8 and r2 have been a big improvement from the 2000 and prior versions.

SSRS (Reporting Services) is still a work in progress, it has really gotten closer to the reporting abilities of Crystal and Access reporting tools. Plus it's integrated which makes it easier to manage and doesn't need a separate server (or license) like Crystal wanted (at least the last version i used did). Tie it into an intranet and create some basic views/stored procs and let the managers create their own reports without them bugging you every month end.

If you're going to go the route of 2k8, I would highly recommend looking into r2. It cleans up some minor issues with SSRS and CDC, but also improves on performance and gives you access to more tools and options. Adding a DATE and TIME data types have also been handy.

And lets not forget.... the best feature of all for 2k8 and r2.... Intellisence for SQL. So worth it.


Just my observations.

Suggestion: If possible, Install on a separate server to test the upgrade impacts across your systems. For us, the impact was almost nonexistent, but for some could be a six month endeavor.

--------------------------------------------------
Stubbornness is a virtue -- if you are right. --Chuck Noll
--------------------------------------------------

 

[wbodger]

So, there is legacy support for DTS packages while I transition them over? I was thinking I would build up the new server, install 2K8 r2, transfer the logins and then attach the db and start testing.

Thanks for the input!

wb

 

[TimeTraveler]

DTS was buggy to begin with the tasks better handled by the app server, imo. If you have a lot of DTS packages to run, or they are complicated, you'll want to set up a parallel system to address that so you when you cut over the SSIS version of your DTS will be in place.

I'm in the middle of a 2K-to-2K8R2-to-Azure migration, and the MS SQL tools are a little more streamlined than 2K. Even so, it's clunky and some things do not work as described. So far I've been unable to directly move a 2K db exported to the 2k8r2 machine to Azure, despite the claim that it'll just take minutes.

Its hard to defend to clients/customers why to hold onto 10-year old server technology. If you think you'll want to go to the cloud at some point, meaning SQL Azure, the tools that come with SQL2K8 (CTP) are required as the source.

Sorry if this didn't directly answer your question, but hope it helps. Bottom line is the migration isn't painless, but there are benefits, to be sure.

S

 

[wbodger]

I ran thru (as a test) moving everything to 2k5. I even ran the DTS upgrade wizard and it said it upgraded all of my packages. However, I then got pulled into other endeavors and haven't had time to go thru them for testing etc. Looks like perhaps I will just remove that VM and start over with 2K8r2 for testing.

Thanks for the input!

wb