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.
When you run a profiler trace against a linked server instance in Microsoft SQL Server 2000, the Audit Logout event does not appear in the trace results file. This problem may occur in the following scenario:
You have one instance of SQL Server 2000 (Instance A).
Instance A has a linked server (Instance B), and Instance B is configured to point to a remote instance of SQL Server 2000.
When you run a profiler trace against Instance B, the Audit Login event appears in the trace results file when Instance A connects to Instance B.
When you run a profiler trace against Instance B, the Audit Logout event does not appear in the trace results file when Instance A disconnects from Instance B.
For a list of all
publicly released SQL Server 2000 post-service pack hotfixes, see the following
article in the Microsoft Knowledge Base:
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.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
How to obtain the latest SQL Server 2000 service pack
You do not have to restart the computer after you apply this
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 of all the
files that you must have to fully update a product to the latest
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.
Linked server connections from SQL Server 2000 clients
rely on connection pooling. After each batch is completed
against the linked server, the client instance sends the sp_reset_connection suffix command to clean up the following connection metadata information:
The accumulated metadata in the sysprocesses
The data columns for the trace event. The data columns can include the CPU time, the read operations,
the write operations, the duration, the start time, and the end time.
Other information, such as error information, temp tables,
and SET options.
After the sp_reset_connection stored procedure is performed, the SPID goes
into Dormant status on the remote linked server instance. You can see the status of the SPID when you query the sysprocesses system table.
SELECT * FROM MASTER.DBO.SYSPROCESSES WHERE Status='Dormant'
If there are no additional queries to the same linked server, the
client instance of SQL Server disconnects the dormant connection to the remote
linked server instance after 5 minutes of inactivity. However, the Audit Logout
event is not produced, even though the connection is disconnected successfully.
This problem does not affect typical applications that use SQLOLEDB
resource pooling, ODBC connection pooling, or SQLClient pooling. Those forms of
pooling issue the internal procedure call to the sp_reset_connection stored procedure as a prefix to
each additional command that is executed. Therefore, connections that are idle
are not reset until a new command comes in. This behavior differs from
the linked server behavior, where the sp_reset_connection command is issued as
a suffix to the last completed command, even if additional commands come later.
In linked server scenarios, the SPID
that has a Dormant status is the one that will soon be disconnected after it is idle,
and that SPID does not produce the Audit Logout trace event. In regular pooling
scenarios, the SPID usually has a Sleeping status when it is idle. After
several minutes of inactivity, depending on how pooling is configured, the
connection is disconnected, and the Audit Logout trace
event is produced.