Moving Data from SQL Server 2000 to SQL Server 2005
(Page 1 of 4 )
This article explains how to move data out of SQL 2000 Server and into SQL Server 2005. This hands-on tutorial shows a step-by-step procedure for moving to SQL 2005, the new database from Microsoft released in November of 2005.
Introduction
There are times when you want to move, to upgrade your living quarters, for example. This analogy is not too bad; you move because you are cramped for space, you don't have the latest fixtures, you take too long to shower because water is trickling and it is not hot. When administrators look at their servers and find that their file system has become cramped, they want to move to another file system, or another machine with more resources.
That's when they start thinking of moving their data or entire database to another physical location. There are a couple of options for doing this, like copying, or backing up the data. There are stored procedures that help you do this, like the sp_attach_singlFile_db, sp_detach_db and sp_attach_db. Microsoft recommends using variants that take advantage of the Create Database for attach procedure, as the older stored procedures will be discontinued in future versions.
In this tutorial the Northwind database on SQL 2000 Server is moved to SQL 2005 server using Enterprise Manager on SQL 2000 Server to detach the database and the SQL Server Management Studio to attach the database. The steps involved are described and illustrated with screen shots of relevant windows of interaction. SQL Server 2005 comes with its own sample database, but familiarity compelled me to move Northwind.
Next: Taking data from SQL 2000 Server >>
More MS SQL Server Articles
More By Jayaram Krishnaswamy
|
| · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | | |
|
/ 77 
