FIX: Performance of a query that is run from a client program on a SQL Server SP3 database is slow after you restart the instance of SQL Server

When a client program runs a query against a Microsoft SQL Server Service Pack 3 (SP3) database, the query may take longer than usual. You may notice this behavior when you do the following:

• You run a query on the SQL Server database by using SQL Query Analyzer while the client program is connected to the database.
• You restart the instance of SQL Server while SQL Query Analyzer is still open.

Additionally, you may notice a message that is similar to the following in the SQL Server error log even when the shared memory network library is turned on: The earlier message indicates that SQL Server is not using the shared memory network library.

You may also notice the following error message in the Windows event log of the computer that is running SQL Server:Note When you close SQL Query Analyzer, you may notice that the response time of the query run from the client program returns to normal

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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 tool in Control Panel. Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

To work around this problem, turn off the shared memory protocol on the computer that is running SQL Server Service Pack 3 (SP3). To do this, follow these steps.

Note Turning off shared memory protocol may cause performance degradation of the computer that is running SQL Server.

1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Client Network Utility.
2. In the SQL Server Client Network Utility dialog box, click the General tab.
3. Click to clear the Enable shared memory protocol check box, and then click OK.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

The problem may affect the performance of applications including the services and Web applications that run on the computer that is running SQL Server SP3. However, working around this problem by turning off shared memory protocol can cause performance degradation on the computer. This behavior occurs because the shared memory network library uses a location in the computer's memory that does not require network or disk access. When you use a network-based protocol such as TCP/IP, the computer uses more memory.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base: