ACC: How to Determine the Version of Catalog Stored Procedures

Last reviewed: May 20, 1997
Article ID: Q95933
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1, 2.0, 7.0, 97

SUMMARY

Advanced: Requires expert coding, interoperability, and multiuser skills.

This article describes how to find the version of catalog stored procedures in Microsoft SQL Server.

MORE INFORMATION

There are situations in which you need to know the version of a stored procedure, such as when you are experiencing difficulties attaching to a SQL Server database. The first method described below uses the System Administration Facility (SAF) in SQL Server to obtain a version number; the second method uses an attached table in Microsoft Access.

Method 1

Using the SAF, log on to SQL Server with a userID and password; using the SQL administrator's login ID (SA) is ideal, but is not always readily available. Once you log on, open the query window and issue the command USE MASTER. This tells SQL Server to use the Master database that contains the system tables. To determine a version, type the following SQL command:

   USE MASTER
   GO
   SELECT Attribute_Value FROM MsServer_Info WHERE Attribute_ID = 500

NOTE: If you are using SQL Server for Windows NT 4.2 or later, substitute spt_server_info for MsServer_Info.

Method 2

In a situation where you can successfully link (attach) SQL Server data, you can link the MsServer_Info table from the Master database to a Microsoft Access database, and then create a query to retrieve the Attribute_Value for the record where the Attribute_ID is equal to 500.

NOTE: If you are using SQL Server for Windows NT 4.2 or later, link to the table spt_server_info instead of MsServer_Info.


Keywords : kbusage OdbcOthr
Version : 1.0 1.1 2.0 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbhowto


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: May 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.