August 30, 2010 at 1:40 pm
Currently running:
SQL Server 2000 SP4+Q899761 (32bit)
on
Microsoft Windows Server 2003
Standard x64 Edition
SP2
I want to upgrade to SQL Server 2005 (64bit)
August 30, 2010 at 1:49 pm
You can do that. I recommend you run the upgrade advisor first though.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 30, 2010 at 1:54 pm
You will not be able to do an in-place upgrade, where the existing server is upgraded, since you are going from 32-bit to 64-bit.
1. script logins/custom messages/jobs/operators from existing server. use sp_help_revlogin to do logins with pws.
2. Perform full backup all databases
3. If upgrading on new hardware, install OS on new server. If using existing server, either uninstall SQL 2000 (if you're going to use the existing instance, or
4. install SQL 2005 x64 on server. You can install as a new named instance to run 2000/2005 in parallel.
5. run scripts to restate logins/messages/jobs/operators on SQL 2008.
This is just a brief overview: Ensure that you read BOL for how to upgrade an existing 2000 to 2005
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 30, 2010 at 2:08 pm
Here is the doc that should be useful and that explains the need to do a side by side for situations such as yours.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 30, 2010 at 2:18 pm
CirquedeSQLeil (8/30/2010)
Here is the doc that should be useful and that explains the need to do a side by side for situations such as yours.
Thanks Jason, I should have put this in my post.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 30, 2010 at 2:25 pm
Oh - one other thing.
Run DBCC CHECKCATALOG while you are in SQL 2000 (you should run DBCC CHECKDB also).
This will detect if any system tables have orphaned records, from where one could manually modify the system tables. It will be easier to fix this in SQL 2000 than in SQL 2005. But just in case, check out this article[/url] for how to fix this corruption in SQL 2005.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
September 4, 2010 at 7:08 pm
Thank you all very much for your knowledgable responses, much appreciated!!!
September 4, 2010 at 8:40 pm
You're welcome.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 8, 2010 at 10:26 am
WayneS (8/30/2010)
You will not be able to do an in-place upgrade, where the existing server is upgraded, since you are going from 32-bit to 64-bit.1. script logins/custom messages/jobs/operators from existing server. use sp_help_revlogin to do logins with pws.
I dont see these specific items listed when I go to generate the script. Would it matter if I scripted all objects to make sure I dont miss anything?
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply