Upgrading from SQl Server 7 to Sql server 2000

[Guest_imported]

Is there any way to restore the registration of all the servers while upgrading from sql server7.0 to Sql server 2000?

 

[tlbroadbent]

Are you asking about the registration properties in SQL Server Enterprise Manager or something else? Terry L. Broadbent - DBA
Computing Links:

http://tlbroadbent.home.attbi.com/prog.htm

faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.

 

[JefB]

We will soon be upgrading SQL7 to SQL2000 and I am curious as to other's experience. In particular, was there any problems with existing Views and/or Stored Procedures?

JefB

 

[Guest_imported]

Yes, we have a number of SQL servers that we are registered under different server groups . We tried upgrading on a test machine and we lost all the server registrations we had registered and there logon information. This is also true if we do a fresh installation of SQL Server 2000 that is does not retain the registrations under SQL Server 7.0. But when we did installation of just Client components of SQL 2000 it did retain the Groups but still not the servers. So we have to individually register all the sql servers again. But there is no issue with existing views, tables or stored procedures as Jef's concern. As fas as upgrade from SQL 7.0 to SQL 2000 is concerned, its a known issue that the SQL profiler traces & server registrations will not be restored to the new system.

 

[tlbroadbent]

For the most part, SQL 7 and SQL 2000 are compatible. However, there are some issues.

Select table..column works in SQL 7 but not in SQL 2000. I've actually found occurrences of this in our databases. A simple typo was not caught by SQL 7 but was caught by the SQL 2000 compiler.

Table names or aliases are no longer allowed in the Update query ... Set statement.

SQL 7 Acceptable syntax:
Update table
Set table.column='abc'

SQL 2000 syntax:
Update table
Set column='abc' -- do not use the table name

Double quotes may cause problems. See Quoted_Identifiers in SQL BOL.

You may find that queries return results in a different order with SQL 2000. You'll have to add Order By clauses to guarantee order.

Read the Backward Compatibility topics in SQL Books Online.

http://msdn.microsoft.com/library/en-us/instsql/in_bckwd_3vlc.asp

http://msdn.microsoft.com/library/en-us/tsqlref/ts_3_bckwrd_1fak.asp

Check the following resources.

[ignore]

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q271566

[/ignore]

http://msdn.microsoft.com/library/en-us/instsql/in_upgrade_5jw3.asp

Terry L. Broadbent - DBA
Computing Links:

http://tlbroadbent.home.attbi.com/prog.htm

faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.