Microsoft KB Archive/909100

= 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 =

Article ID: 909100

Article Last Modified on 11/2/2007

-

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 &quot;More information&quot; 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
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
 * The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.

Note This issue does not occur on systems that use the Intel Itanium processor architecture.
 * The system is running a 64-bit version of the Microsoft Windows Server operating system.
 * The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

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:

http://support.microsoft.com/contactus/?ws=support

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.

64-bit hotfix for Itanium processors


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 &quot;Applies to&quot; 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.
 * 1) 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

Keywords: kbhotfixserver kbbug kbfix kbtshoot kbqfe kbpubtypekc KB909100

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.