Migrating from 7.0 to 2000

[MagnumVP]

I've been put in charge of migrating the Data of the SQL 7.0 server on a NT 4.0 Server to a server running Windows 2003 running SQL 2000. I still have to create the Windows 2003 and install SQL 2000.

I would try to upgrade the exisitng server but it a REALLY old (6 years) and the server just can't handle 2003.

I'm a novice at SQL so any help would be help.

 

[MagnumVP]

After working on it all day and figure out a few things here is some more information that I have.

The 7.0 Server is running 1 DB with only 10 users.

The SQL 2000 Server is installed as the default instance with SP3a. I've tried to use the Copy DB wizard with no luck. I even tried to backup the 7.0 DB and then try to restore it to the 2000 but that didn't work. I've even tried to detach it from the 7.0 and then attach it on the 2000. That worked, but the information wasn't there and I'm not sure why (remember I'm just beginning).

The attaching it seemed to work and I was able to log in but all the data wasn't there. Well it was. When I iipen up the data in Access the table strucure and data are there, but when I open up the Program that uses the data it doesn't recognize it. I can log in but the data just isn't there.

Any thoughts?

 

[SpiderBear6]

That's interesting, the detach from 7 and attach to 2000 should have worked. Maybe the program is configured to connect to a SQL Server 7 db and as such can't understand the SQL Server 2000 db.

Hope that helps.

--------------------------------------
"We are star-stuff. We are the universe made manifest trying to figure itself out."
-- Delenn in Babylon 5 - "A Distant Star"

 

[MagnumVP]

Spider.... you were partially correct. I guess the Detached and attached method did work, but because our Support contract expired they would help me migrate it over to 2000. However, they did tell me that there is something in the program itself that you have to configure for it to allow migration.

What ever the case may be, they wanted $12,000 to migrate the program over. I talked it over with everyone that uses it and we are going to scrap the program and use another one that doesn't cost nearly that much.