INF: SQL Server May Not Be Detected as Windows NT Version

ID: Q121023

The information in this article applies to:

Microsoft SQL Server version 4.2

SUMMARY

SQL Server for Windows NT may not always be identified to the SQL Server tools as a Windows NT version of SQL Server if the installation SQL scripts are not run in the proper sequence.

MORE INFORMATION

When SQL Server Setup is building the master database, it runs several scripts to build the system objects used by SQL Server and its tools. These scripts are stored in the c:\sql\install directory:


   Instmstr.Sql, Instcat.Sql, Instnt.Sql, Admin2.Sql, Object2.Sql

The operations performed by these scripts are discussed on page 8 of the Microsoft SQL Server "Configuration Guide."

Sometimes sites may run one or more of these scripts to restore system objects. Users wanting to restore all of the system objects in their master database should run the scripts in the order specified.

Any time the script INSTMSTR.SQL is run against a SQL Server for Windows NT system, users must also run the INSTNT.SQL script. Failure to also run the INSTNT.SQL script will lead to the following behavior:


   Transfer manager will not connect to the server as a
   destination server, saying it is not a Windows NT server.

   The maximum allowed value for sp_configure memory will be only
   32000 instead of the normal value of 1048576.

SQL Administrator 4.21 will exhibit the following behavior (the 4.20 version of SQL Administrator does not):


   The Truncate Only and No_log options will be greyed out on
   the scheduled backups add event window.

The following options will be greyed out on the System/Manage/Consistency Check window.


   Checkdb:     Do not check indexes
   Checkalloc:  Do not check indexes and
                Continue after error

   Check Text Allocations: All options

The Database\Backup Restore\Tape directory and the Database\Backup Restore\Backup Restore window tape functions will be greyed out or disabled.

Any site experiencing these symptoms can resolve them by simply running the INSTNT.SQL script:


   cd \sql\install
   isql /Usa /P<password> /iinstnt.sql /oinstnt.out

These symptoms could also occur if a site copied an OS/2 SQL Server MASTER.DAT over to a Windows NT server and then ran SQL Server for Windows NT without first running INSTNT.SQL as documented in the section titled "Before Upgrading from Version 4.2 for OS/2" in the Server Installation' chapter of the Microsoft SQL Server "Configuration Guide."

Additional query words: Windows NT grayed

Keywords : kbtool SSrvSQL_Admin SSrvWinNT
Version : 4.2
Platform : WINDOWS
Issue type :