BUG: SQL Monitor Parameters and NETSQL.EXE

 Last reviewed: May 5, 1997
Article ID: Q93048

The information in this article applies to:
  • Microsoft SQL Server, version 4.2a
BUG# 7823 (4.2)

SYMPTOMS

When attempting to set the parameters for SQL Monitor from the command line using the NETSQL command on LAN Manager-based networks, the following occurs:

  • The value for the second parameter passed is not set correctly.
  • It does not display the Logsize parameter.
  • The value for the sqltimeout parameter (180 by default) is incorrectly shown as the value of the Logsize parameter (4096 by default).

For example, assuming the default values for the SQL Monitor parameters are not changed in LANMAN.INI, executing 

   Netsql start sqlmonitor /backuptime=10 /monitortime=10
 /monitortablesize=500
followed by 

   Netsql config sqlmonitor
shows the following output: 

   Monitor is                                 off
   Monitor wakeup interval (seconds)          60
   Backup is                                  On
   Backup wakeup internal (minutes)           10
   Max rows allowed in monitor table          500
   SQL Query/Login timeout interval           1024

STATUS

Microsoft has confirmed this to be a problem in SQL Administrator 4.2a. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: lanman
Keywords : kbbug4.20a kbtool SSrvMon SSrvSQL_Admin
Version : 4.2a
Platform : OS/2

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