INF: Running SQL Server 6.5 INSTCAT.SQL on SQL Server 6.0.

 Last reviewed: April 9, 1997
Article ID: Q154644

The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5

SUMMARY

When you run INSTCAT.SQL included in SQL Server 6.5 on SQL Server 6.0, an error message appears which indicates that procedure sp_MS_upd_sysobj_category does not exist. You may ignore this message.

MORE INFORMATION

The procedure sp_MS_upd_sysobj_category in SQL Server 6.5 replaces the procedure sp_check_objects in SQL Server 6.0. When you run sp_MS_upd_sysobj_category on SQL Server 6.0, the SQL Server 6.5 INSTCAT.SQL runs sp_check_objects if it is present. This indicates that the correct processing is done on SQL Server 6.0. INSTCAT.SQL successfully completes all necessary processing against SQL Server 6.0 without sp_MS_upd_sysobj_category.

For some users who notice that the error may find that sp_MS_upd_sysobj_category is created by the UPGRADE1.SQL script in the SQL Server 6.5 \mssql\install directory, and attempt to run UPGRADE1.SQL against SQL Server 6.0. This is not necessary. In addition, UPGRADE1.SQL does not complete successfully against SQL Server 6.0.

Additional query words: 2.65.0201 6.0 6.5
Keywords : kbnetwork SSrvGen SSrvInst
Version : 2.65.0201 6.0 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.