FIX: The performance of the statement that raises an error differs from the performance of the statement that does not raise an error when you trace exception events in SQL Server 2000 on an IA-64 computer (909100)



The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition

BUG #: 474717 (SQL Server 8.0)
BUG #: 474808 (SQL Server 8.0)
BUG #: 22 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

When you trace exception events in Microsoft SQL Server 2000 on an IA-64 computer, the performance of the statement that raises an error differs from the performance of the statement that does not raise an error.

Note For more information about how to trace exception events in SQL Server 2000, see the "More information" section.

For example, you have a statement that inserts an already existing value into a primary key column of a table. When you run the insert statement, you receive an error message that resembles the following:
Server: Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key in object 'Table1'.
The statement has been terminated.
Additionally, you can see the error in the SQL Profiler trace output. If you repeatedly run this insert statement for several hours, some executions of the statement take a much longer time to display this error message. Alternatively, you can use the SQL:StmtCompleted event class to record the duration for every execution of the statement. The duration of some executions of the statement are much longer than the duration of the rest.

This example shows a scenario in which you encounter this problem. This problem may be observed with other error numbers in addition to error 2627.

For a list of all publicly released SQL Server 2000 post-Service Pack 4 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

  • Microsoft SQL Server 2000 Service Pack 4 (SP4)

    For information about how to obtain SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:

    290211 How to obtain the latest SQL Server 2000 service pack

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.32-bit hotfix
File nameFile versionFile sizeDateTimePlatform
Spupdsvc.exe6.2.24.022,75202-Jun-200502:43x86
Tempcatsign.cdfNot Applicable1,79610-Mar-200600:51Not Applicable
80sp4-tools.sqlNot Applicable134,62819-Feb-200600:40Not Applicable
Dtsui.dll2000.80.2187.01,593,34409-Mar-200619:47x86
Impprov.dll2000.80.2187.0102,40009-Mar-200619:47x86
Msgprox.dll2000.80.2187.094,20809-Mar-200619:47x86
Msrpjt40.dll4.10.9424.0188,47324-Jan-200607:13x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200521:46x86
Ntwdblib.dll2000.80.2187.0290,81609-Mar-200619:47x86
Odsole70.dll2000.80.2187.069,63209-Mar-200619:47x86
Osql.exe2000.80.2187.057,34409-Mar-200617:37x86
Pfclnt80.dll2000.80.2187.0430,08009-Mar-200619:47x86
Procsyst.sqlNot Applicable552,06816-Jun-200523:15Not Applicable
Replmerg.exe2000.80.2187.0163,84009-Mar-200617:46x86
Replmerg.sqlNot Applicable1,151,45009-Mar-200617:22Not Applicable
Replprov.dll2000.80.2187.0237,56809-Mar-200619:47x86
Replrec.dll2000.80.2187.0315,39209-Mar-200619:47x86
Replsub.dll2000.80.2187.0270,33609-Mar-200619:47x86
Repltran.sqlNot Applicable1,000,63402-Feb-200620:59Not Applicable
Semexec.dll2000.80.2187.0856,06409-Mar-200619:47x86
Sp4_serv_qfe.sqlNot Applicable18,81016-Jun-200523:15Not Applicable
Sqlagent.exe2000.80.2187.0323,58409-Mar-200617:26x86
Sqldiag.exe2000.80.2187.0118,78409-Mar-200618:22x86
Sqldmo.dll2000.80.2187.04,362,24009-Mar-200619:47x86
Sqlevn70.rll2000.80.2187.045,05609-Mar-200619:47Not Applicable
Sqlfth75.dll2000.80.2187.0102,40009-Mar-200617:35x86
Sqlservr.exe2000.80.2187.09,162,75209-Mar-200619:45x86
Sqlsort.dll2000.80.2187.0589,82409-Mar-200619:47x86
Stardds.dll2000.80.2187.0176,12809-Mar-200619:47x86
Svrnetcn.dll2000.80.2187.0110,59209-Mar-200619:47x86
Ums.dll2000.80.2187.035,32809-Mar-200619:47x86
Osql.exe2000.80.2187.057,34409-Mar-200617:37x86
Sqlse.rll1.1.2032.045,05622-Feb-200621:50Not Applicable
Sqlstpcustomdll.dll1.1.2032.01,846,78422-Feb-200621:50x86
Sqlstpcustomdll.rll1.1.2032.012,28822-Feb-200621:50Not Applicable
64-bit hotfix
File nameFile versionFile sizeDateTimePlatform
80sp4-tools.sqlNot Applicable134,62819-Feb-200600:40Not Applicable
Dtsui.dll2000.80.2187.01,593,34409-Mar-200619:47x86
Impprov.dll2000.80.2187.0102,40009-Mar-200619:47x86
Msgprox.dll2000.80.2187.094,20809-Mar-200619:47x86
Msrpjt40.dll4.10.9424.0188,47324-Jan-200607:13x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200521:46x86
Ntwdblib.dll2000.80.2187.0290,81609-Mar-200619:47x86
Odsole70.dll2000.80.2187.069,63209-Mar-200619:47x86
Osql.exe2000.80.2187.057,34409-Mar-200617:37x86
Pfclnt80.dll2000.80.2187.0430,08009-Mar-200619:47x86
Procsyst.sqlNot Applicable552,06816-Jun-200523:15Not Applicable
Replmerg.exe2000.80.2187.0163,84009-Mar-200617:46x86
Replmerg.sqlNot Applicable1,151,45009-Mar-200617:22Not Applicable
Replprov.dll2000.80.2187.0237,56809-Mar-200619:47x86
Replrec.dll2000.80.2187.0315,39209-Mar-200619:47x86
Replsub.dll2000.80.2187.0270,33609-Mar-200619:47x86
Repltran.sqlNot Applicable1,000,63402-Feb-200620:59Not Applicable
Semexec.dll2000.80.2187.0856,06409-Mar-200619:47x86
Sp4_serv_qfe.sqlNot Applicable18,81016-Jun-200523:15Not Applicable
Sqlagent.exe2000.80.2187.0323,58409-Mar-200617:26x86
Sqldiag.exe2000.80.2187.0118,78409-Mar-200618:22x86
Sqldmo.dll2000.80.2187.04,362,24009-Mar-200619:47x86
Sqlevn70.rll2000.80.2187.045,05609-Mar-200619:47Not Applicable
Sqlfth75.dll2000.80.2187.0102,40009-Mar-200617:35x86
Sqlservr.exe2000.80.2187.09,162,75209-Mar-200619:45x86
Sqlsort.dll2000.80.2187.0589,82409-Mar-200619:47x86
Stardds.dll2000.80.2187.0176,12809-Mar-200619:47x86
Svrnetcn.dll2000.80.2187.0110,59209-Mar-200619:47x86
Ums.dll2000.80.2187.035,32809-Mar-200619:47x86
64-bit hotfix for Itanium processors
File nameFile versionFile sizeDateTimePlatform
Impprov.dll2000.80.2187.0244,73610-Mar-200605:56Not Applicable
Msgprox.dll2000.80.2187.0188,41610-Mar-200605:56Not Applicable
Mssdi98.dll8.11.50523.0758,78410-Mar-200605:56Not Applicable
Msvcr71.dll7.10.3052.4348,16010-Mar-200605:56Not Applicable
Odsole70.dll2000.80.2187.0150,52810-Mar-200605:56Not Applicable
Osql.exe2000.80.2187.0149,50410-Mar-200605:56Not Applicable
Pfclnt80.dll2000.80.2187.01,187,84010-Mar-200605:56Not Applicable
Pfclnt80.dll2000.80.2187.0430,08010-Mar-200605:56Not Applicable
Procsyst.sqlNot Applicable552,06810-Mar-200605:56Not Applicable
Replmerg.exe2000.80.2187.0375,29610-Mar-200605:56Not Applicable
Replmerg.sqlNot Applicable1,151,45010-Mar-200605:56Not Applicable
Replprov.dll2000.80.2187.0538,62410-Mar-200605:56Not Applicable
Replprov2.dll2000.80.2187.0538,62410-Mar-200605:56Not Applicable
Replrec.dll2000.80.2187.0775,16810-Mar-200605:56Not Applicable
Replrec2.dll2000.80.2187.0775,16810-Mar-200605:56Not Applicable
Replsub.dll2000.80.2187.0641,02410-Mar-200605:56Not Applicable
Repltran.sqlNot Applicable1,000,63410-Mar-200605:56Not Applicable
Sqlagent.exe2000.80.2187.01,061,37610-Mar-200605:56Not Applicable
Sqldiag.exe2000.80.2187.0334,33610-Mar-200605:56Not Applicable
Sqldmo.dll2000.80.2187.04,362,24010-Mar-200605:56Not Applicable
Sqldmo.dll2000.80.2187.013,860,35210-Mar-200605:56Not Applicable
Sqlevn70.rll2000.80.2187.035,32810-Mar-200605:56Not Applicable
Sqlfth75.dll2000.80.2187.0246,78410-Mar-200605:56Not Applicable
Sqlservr.exe2000.80.2187.024,937,47210-Mar-200605:56Not Applicable
Sqlservr.pdbNot Applicable21,146,62410-Mar-200605:56Not Applicable
Sqlsort.dll2000.80.2187.0617,47210-Mar-200605:56Not Applicable
Svrnetcn.dll2000.80.2187.0427,52010-Mar-200605:56Not Applicable

WORKAROUND

To work around this problem, avoid continually tracing the exception event in SQL Server 2000 on an IA-64 computer.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

To trace exception events in SQL Server 2000, follow these steps:
  1. Open SQL Profiler, create a new trace, and then connect to the instance of SQL Server.
  2. In the Trace Properties dialog box, click the Events tab.
  3. Under Available event classes, expand Errors and Warnings, and then double-click Exception.

    The Exception event class appears under Selected event classes.
  4. Click Run.
Alternatively, create a server side trace to trace exception events in SQL Server 2000. To do this, follow these steps:
  1. Create the trace definition by using the sp_trace_create stored procedure.
  2. Add the exception event to the trace by running the sp_trace_setevent stored procedure and set @eventid = 33 together with other parameters.
  3. Start the trace by running the sp_trace_setstatus stored procedure.
For more information about these stored procedures, see the following topics in SQL Server 2000 Books Online:
  • sp_trace_create
  • sp_trace_setevent
  • sp_trace_setstatus
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbHotfixServer kbBug kbfix kbtshoot kbQFE kbpubtypekc KB909100 kbAudITPRO kbAudDeveloper