August 10, 2008 at 8:00 pm
I don't think there is any problem with what I'm trying to do, but I thought I would give my example and see what anyone can come up with.
Without going into all the specifics I'll try to be brief.
Current Setup(at least the part in the first phase):
1. Server 1 : SQL Server 2000 (32-bit) on x86. DTS package builds datawarehouse from server 2.
1. Server 2 : SQL Server 2000 (32-bit) on x64. Main production box.
Phase 1
1. New Server 1 : SQL Server 2005 (64-bit) on x64. DTS package will be adapted to do same thing from Server 2.
2. Server 2 : Remains the same for now.
From what I can remember I don't think there are any gotchas here besides catching any logins, dts packages, or agent jobs. The accounts will run under the same name that they always have. We can't do an upgrade install because of going to x64 so it'll basically be a rebuild.
Are there any gotchas that I'm not thinking about for 2005 building it's data from 2000 dbs?
Thanks
MCITP, Database Administrator
A hodgepodge of Information Technology and Life
LinkedIn Profile
My Twitter
August 11, 2008 at 1:24 am
Update all statistics after the upgrade to 2005. The 2005 optimiser doesn't much like the 2000 style statistics.
Also, as far as I know, there is no 64-bit version of dtsrun, which is the program that runs DTS packages. It should be possible to run the 32 bit version on the 64 bit server, but test carefully.
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
August 11, 2008 at 7:12 am
yea, we are already running 64bit OS with 32bit SQL.
If it's 2005 and the DTS package (legacy) or SSIS package runs from 2005 and builds its data from a 2000 database there's still a need to update the statistics?
If it's rebuilding the database from scratch I wouldn't think we'd need to update the stats.
MCITP, Database Administrator
A hodgepodge of Information Technology and Life
LinkedIn Profile
My Twitter
August 11, 2008 at 9:21 am
Update the statistics of any database that you upgrade from SQL 2000 to SQL 2005.
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
August 11, 2008 at 9:39 am
Maybe I need to clarify.
The SQL Server 2005 instance on Server 1 will be building a database from the data contained in a SQL Server 2000 instance on Server 2.
An SSIS package will be updating and inserting data back and forth between the two.
This is a nightly job that is currently a DTS package. I am converting it to SSIS.
MCITP, Database Administrator
A hodgepodge of Information Technology and Life
LinkedIn Profile
My Twitter
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply