Having Some Issues Migrating to a New Server

The Setup: I'm moving a SQL Server 7 Database from a SQL Server sp'd somewhere between 3 and 4 (7.00.1028) to a SQL Server without any service packs. The old machine is a Dell PowerEdge 2400 (about 3 years old) and the new machine is a Dell PowerEdge 2650 with dual gigabit nics (and I have them teamed). Both machines run Windows 2000 Server. Mostly default installation on both the OS and SQL Server.

The Problem: When I restore the database to the new server (and resolve the orphaned login issues, etc.) the server hangs unbelievably. Most of my users can't even connect, much less work in their vb apps. I can ping the machine, but can't run the simplest T-SQL against it.

Any ideas?

Help would be greatly appreaciated.Any information from SQL Server error log, event viewer and any other logs that can help to assess the situation.

Ensure to upgrade to latest service pack on SQL & OS.|||Originally posted by Satya
Any information from SQL Server error log, event viewer and any other logs that can help to assess the situation.

Ensure to upgrade to latest service pack on SQL & OS.

Log showed that SQL Server had been installed before sys tech changed the name of the machine . . . think that may be the problem as log was reporting old name instead of new name. Removed SQL Server and reinstalling . . . we'll see . . .|||If the hostname is changed then you must use SP_DROPSERVER & SP_ADDSERVER to take affect the new name.

Refer to books online for more information.|||Originally posted by Satya
If the hostname is changed then you must use SP_DROPSERVER & SP_ADDSERVER to take affect the new name.

Refer to books online for more information.

Thanks a bunch for the info . . . will let you know if that was the problem.|||Several issues, but the most obvious one to address first is to install SP3 before you start restoring the database. Any hidden reason why it was not done in the first place?|||Originally posted by rdjabarov
Several issues, but the most obvious one to address first is to install SP3 before you start restoring the database. Any hidden reason why it was not done in the first place?

Tech who started the job thought that he could just install it after the db had been restored. I've since brought the current server to sp4 and upgraded the new server to sp4 as well. MS says this should not be a problem (restoring sp3 database to nosp server), but they've given me bad advice before!|||The reason they said it because you certainly can do it. The trick is that you shouldn't ;)|||Originally posted by rdjabarov
The reason they said it because you certainly can do it. The trick is that you shouldn't ;)

No Doubt.|||Trying to restore a database to another server with a prior service pack level is a very bad idea. I've lost lots of hair that way!

MS-SQL 7 sp3 actually changed the structure of some system tables (sysindexes if I remember right, and possibly others). Restoring a post sp3 database to a "gold" server will effectively "lock the box", or at least it did that for me.

-PatP|||Originally posted by Pat Phelan
Trying to restore a database to another server with a prior service pack level is a very bad idea. I've lost lots of hair that way!

MS-SQL 7 sp3 actually changed the structure of some system tables (sysindexes if I remember right, and possibly others). Restoring a post sp3 database to a "gold" server will effectively "lock the box", or at least it did that for me.

-PatP

Sounds exactly like our case here.|||you need to find to get SP3
______________________________
Reza Bashash www.bashash.com|||You can download SP3 for ver.7 from MS homepage or if not search under google.