March 18, 2009 at 4:51 pm
Hello Everyone,
I am about to migrate the sql server 2000 for our production servers. I got 5 SQL server at work. I need to migrate all the servers in next few weeks. When I look on the microsoft website sql 2008 got more features then 2005, for example Data Compression and Backup Compression. About the money wise, both version are the same whatever you go for Standard or Enterprise. Before I decide my self, I want you guy to suggest me which SQL version I should go for, 2005 or 2008? Standard or Enterprise? Enterprise is very expensive compare with the Standard.
I am using lots of DTS packages and Link Servers, I can transfer DTS packages to Legacy part using SQL DTS Designer components.
What should I prepare before I migrate?
Thanks.
Leo
March 18, 2009 at 7:41 pm
Support cycles being what they are, if I were upgrading today (and I am), I'd be going for 2008, not 2005. At this point, it's four years into the 2005 support cycle. That's four years less you're going to get. 2008 is good to go.
As far as Standard or Enterprise... we run a mix, mostly Standard, some Enterprise. It really depends on if you can put the Enterprise stuff to work. If so, it's worth the money, but if you're not really going to use most, if not all the Enterprise functionality, it might not be worth it.
Get the Upgrade Advisor from Microsoft. Run it against your systems and listen to it's advice. Also, I'd suggest, if you can, doing side-by-side upgrades, backing up your 2000 system and then restoring to a 2008 system instead of inplace upgrading the 2000 system. DTS is the worst part of the upgrade process. Some packages will move easily. Some won't and will have to be rewritten.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 22, 2009 at 4:48 pm
Hi Grant,
I have a couple of questions here,
1. What about detach the database in 2000 and reattach in 2008? It should be okay, isn't it?
2. About the Upgrade Advisor, will it tell me what version(enterprise,standard) I will required to migrate when I run the upgrade advisor on my SQL 2000 production server?
3. ** One of our IT specialist suggested me that I should install sql 2008 cluster server instead of normal sql 2008 server, any advantages for that? I am not familiar with cluster server. What about disadvantages?
4. We bought Dell Server which included SQL 2005 standard version of it, is that able to transfer the license to sql 2005 to sql 2008? I don't think microsoft won't let us to do it, isn't it?
Thanks.
Leo
March 22, 2009 at 5:42 pm
Leo (3/22/2009)
1. What about detach the database in 2000 and reattach in 2008? It should be okay, isn't it?
There are 3 steps you need to follow after you re-attach a SQL-2000 database on a sql-2008 instance (and change the compatibility level from 80 to 100):
1.Execute DBCC CHECKDB WITH DATA_PURITY to check the database for column values that are not valid or are out of range. After you have successfully run DBCC CHECKDB WITH DATA_PURITY against an upgraded database, you do not need to specify the DATA_PURITY option again because SQL Server will automatically maintain "data purity." This is the only DBCC CHECKDB check that you need to run as a post-upgrade task.
2.Run DBCC UPDATEUSAGE to correct any incorrect page or row counts.
USE dbName;
go
DBCC UPDATEUSAGE (dbName)
GO
3.Update statistics by using the sp_updatestats stored procedure to ensure all statistics are up-to-date.
See the following link for more info:
SQL Server 2008 Upgrade Technical Reference Guide:
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
March 23, 2009 at 6:21 am
Leo (3/22/2009)
Hi Grant,I have a couple of questions here,
1. What about detach the database in 2000 and reattach in 2008? It should be okay, isn't it?
Sure. I just like the backup & restore method because it leaves the other database online, just in case.
[/quote]
2. About the Upgrade Advisor, will it tell me what version(enterprise,standard) I will required to migrate when I run the upgrade advisor on my SQL 2000 production server?
[/quote]
It will tell you that you have functionality that requires Enterprise, but it won't recommend a version.
3. ** One of our IT specialist suggested me that I should install sql 2008 cluster server instead of normal sql 2008 server, any advantages for that? I am not familiar with cluster server. What about disadvantages?
That's a rather big topic. My local admin specialist hates SQL clusters. We have had some pretty bad experiences with them, but others do not. I'd be hard pressed to recommend one way or the other.
[/quote]
4. We bought Dell Server which included SQL 2005 standard version of it, is that able to transfer the license to sql 2005 to sql 2008? I don't think microsoft won't let us to do it, isn't it?
Thanks.
Leo[/quote]
I'm not sure about the last one, but I doubt it. You'd have to contact MS to be sure.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply