Upgrade Microsoft SQL server 7.0 to 2000 1

[Nats79]

Hi,
I am doing research/preparation on upgrading from SQL 7 to 2000.I came across some notes saying that there are some upgrade issues.Two issues which affect me are objects that have been renamed using the sp_rename stored procedure and stored procedures that reference system tables.These will apparently not be converted/created in the new database.How can I overcome/resolve these issues?

Also,if I upgrade the current server(instead of doing a clean install on a new machine)according to the Microsoft steps,it looks to me that
the only steps that need to be followed are:
- run setup from the cd to upgrade the existing installation
- repopulate full-text catalogs
- update statistics
- upgrade the meta data services tables and the repository database

What about transferring logins,scripting the jobs etc.?
Do I no longer need to worry about these steps? Are these automatically included in the upgrade?

What about the dts packages? Do they also get copied/upgraded to automatically? I haven't seen anything anywhere that requires you to copy/backup the packages.

Thanks in advance!

 

[fluteplr]

All the other items are upgraded automatically when you do an inplace upgrade. DTS packages are also upgraded IF they are stored as local packages, other types of storage may be upgraded but I have never tested that.

I have not seen any problems with the sp_reanme issue. The problem with the referencing system tables is that some of the system tables have changed so that old references will be bad.

My suggestion is the following. If you have a second (test) server available. Create a 7 install on that server, do the upgrade and TEST a lot. You will then be in a position to know what the issues will actually be.

 

[Corran007]

fluteplr covered alot

Dont know anything about sp_rename. As for those that reference system, depending on what you were referencing may have changed.They may be gone or just moved. You will have to test.
If you upgrade the current, the system really does not change so the jobs, logins, etc all still stay. What i will say about the upgrade is that you do not get any options when upgrading if you want to change any configurations. This is why i have done new machine installs instead of upgrades.

as fluteplr suggested, get a second box and configure the system like yours is currently then do an upgrade. TEST, TEST, TEST.

 

[Nats79]

Ok,it looks like i'm going to go the side-by-side installation route.

I just wanted to make sure,if i install 2000 as a named instance will i then have to change the connection path in all my client applications in order for it to connect to SQL server 2000?

Thanks in advance

 

[Corran007]

Correct. What we do is have our old server serverx. and when we are setting up or new transfer its serverxA. We send evertying over to the new server. we then remove the old from the domain and take it off the network. Then we change the name of serverxA to serverX and readd it to the domain. I think thats what we do. This allivates us having to change anything that connects to it since it is the same name when we finish