 |  |  |  |  |  |  |  |
SQL ,migration or export ?
Please support our MS SQL advertiser: Intel Parallel Studio Home
 |
Hi everybody,
I've got a big pb, and I need help.....
I have to use MS SQL Server 2005 SP2 Enterprise Edition instead of
MSSQL Server 2000 Enterprise Edution and I don't know how to use the old SQL 2000 db.
Any sugestions?
Thanks for your time.
Eddysonys
I've got a big pb, and I need help.....
I have to use MS SQL Server 2005 SP2 Enterprise Edition instead of
MSSQL Server 2000 Enterprise Edution and I don't know how to use the old SQL 2000 db.
Any sugestions?
Thanks for your time.
Eddysonys
•
•
Join Date: Jun 2005
Posts: 60
Reputation: 
Solved Threads: 5
Junior Poster in Training
You have two options, both explained in books on line.
1) UPGRADE the server. This will upgrade your server from 2000 to 2005. It is a one way move and the whole server is changed. There is no rollback for this.
2) MIGRATE the database. This is a lot more difficult as the DBA (er.. you?) has to a) set up a new server (or server instance), b) make sure that all of the relevant logins / users etc are on the new server, c) copy (through SQL or DTS or SSIS or BCP) the data into a new DB and new tables (use Generate SQL Script for this) and then make sure that all stored procedures, triggers, functions and user data types are transfered as well.
The advantage of option 2 is that you can continue to use your original DB and apps while you set everything up and then you have a fall back position (the original DB).
Given the choice I use option 2.
1) UPGRADE the server. This will upgrade your server from 2000 to 2005. It is a one way move and the whole server is changed. There is no rollback for this.
2) MIGRATE the database. This is a lot more difficult as the DBA (er.. you?) has to a) set up a new server (or server instance), b) make sure that all of the relevant logins / users etc are on the new server, c) copy (through SQL or DTS or SSIS or BCP) the data into a new DB and new tables (use Generate SQL Script for this) and then make sure that all stored procedures, triggers, functions and user data types are transfered as well.
The advantage of option 2 is that you can continue to use your original DB and apps while you set everything up and then you have a fall back position (the original DB).
Given the choice I use option 2.
Tk's very much , pclfw!
I will keep U posted with my evolution.It seems harder , the 2-nd option, but I'll start with this one.
See U.
I will keep U posted with my evolution.It seems harder , the 2-nd option, but I'll start with this one.
See U.
|
Similar Threads
- Migrating database made easy (Windows Software)
- Help with automatic update problem and more (Viruses, Spyware and other Nasties)
- IT Project/Implementation Consultant for hire (Post your Resume)
- load data infile - fails to load my db2 del (ascii) file (MySQL)
- PHPMyAdmin -> MSSQL (MySQL)
Other Threads in the MS SQL Forum
- Previous Thread: Copying ASP.NET's default member info database
- Next Thread: Read row in a CLR Stored Procedure Without output parameter
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest MS SQL Posts
- Today's Posts
- Unanswered Threads
