How to upgrade the catalog stored procedures
This procedure is needed only when:
- Running a new Microsoft® SQL Server™ 2000 ODBC driver against an earlier version of SQL Server.
- Running a new SQL Server OLE DB provider against an earlier version of SQL Server.
- Referencing an earlier version of SQL Server in an sp_addlinkedserver, OPENROWSET, or OPENQUERY statement running on a new version of SQL Server. These statements use the SQL Server OLE DB provider to access the target SQL Server.
To ensure the proper operation of the SQL Server OLE DB provider or SQL Server ODBC driver, you must use the Instcat.sql script that comes with your new version of SQL Server to upgrade the catalog stored procedures on the earlier version of SQL Server. For example, when running the SQL Server version 7.0 ODBC driver against SQL Server 6.5, you must run the SQL Server 7.0 version of Instcat.sql against SQL Server 6.5.
To upgrade the catalog stored procedures
To upgrade the catalog stored procedures, the system administrator runs a script by using the isql utility. To run isql, the computer must be installed as a client workstation for SQL Server. The system administrator should back up the master database before running Instcat.sql.
At a command prompt, use the isql utility to run the Instcat.sql script. For example:
C:> ISQL -Usa -Psa_password -Sserver_name -ilocation\Instcat.sql
Arguments
sa_password
Is the password of the system administrator.
server_name
Is the name of the server on which SQL Server resides.
location
Is the full path of the location of Instcat.sql. You can use Instcat.sql from an installed SQL Server (the default location is C:\Mssql7\Install) or from the SQL Server compact disc (the default location is D:\platform where D: is the CD-ROM drive letter and platform is the appropriate server platform directory, such as 386).
The Instcat.sql script generates many messages. Most of these indicate how rows were affected by Transact-SQL statements issued by the script. These messages can be ignored, although the output should be scanned for messages that indicate an execution error. When Instcat.sql is run against a version 6.0 SQL Server, the message generated about the object sp_MS_upd_sysobj_category not existing can be ignored. The last message should indicate that Instcat.sql completed successfully.
The Instcat.sql script fails when there is not enough space available in the master database to store the catalog stored procedures or to log the changes to existing procedures. If the Instcat.sql script fails, contact your system administrator.