FIX: No Data in ODBC Performance Log If Stopped/Restarted

Last reviewed: September 8, 1997
Article ID: Q157801

The information in this article applies to:

Microsoft SQL Server, version 6.5
Microsoft Open Database Connectivity, version 2.65

BUG #: 16051 (Windows: 2.65)

SYMPTOMS

If an Open Database Connectivity (ODBC) application stops and then restarts, the ODBC driver's performance statistics will log the following:

   retcode = SQLSetConnectOption
             (hdbc,
             SQL_COPT_SS_PERF_DATA,
             SQL_PERF_STOP);
   retcode = SQLSetConnectOption
             (hdbc,
             SQL_COPT_SS_PERF_DATA,
             SQL_PERF_START);

The log file will only have its header information; it will not contain any data.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft SQL Server ODBC Driver version 2.65. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Additional query words:
Keywords : kbbug6.50 kbfix6.50.sp2 SSrvErr_Log SSrvGen kbinterop
Version : 2.65 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: September 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.