Article ID: 836136 - Last Review: February 12, 2007 - Revision: 3.2

FIX: The compile time for a query that uses at least one outer join may be greater for SQL Server post-SP3 builds

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Bug #: 470969 (SQL Server 8.0)

On This Page

Expand all | Collapse all

SYMPTOMS

When you run a query that uses at least one outer join, the compile time for the query may be greater for Microsoft SQL Server 2000 post-SP3 hotfix build 8.00.0780 or later when it is compared to the compile time for SQL Server 2000 Service Pack 3 (SP3).
Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211  (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack
Back to the top

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.
  
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   30-Jan-2004  16:29  2000.80.911.0      33,340  Dbmslpcn.dll     
   30-Jan-2004  16:29  2000.80.911.0      90,692  Msgprox.dll      
   30-Jan-2004  16:29  2000.80.911.0      62,024  Odsole70.dll     
   30-Jan-2004  16:29  2000.80.911.0      25,144  Opends60.dll     
   30-Jan-2004  16:28  2000.80.911.0      57,904  Osql.exe         
   30-Jan-2004  16:29  2000.80.911.0     221,768  Replprov.dll     
   30-Jan-2004  16:29  2000.80.911.0     307,784  Replrec.dll      
   30-Jan-2004  16:29  2000.80.911.0     287,304  Rinitcom.dll     
   30-Jan-2004  16:29  2000.80.911.0      57,916  Semnt.dll        
   30-Jan-2004  16:28  2000.80.911.0      28,672  Sqlagent.dll     
   30-Jan-2004  16:29  2000.80.911.0     311,872  Sqlagent.exe     
   30-Jan-2004  16:29  2000.80.911.0   4,215,360  Sqldmo.dll       
   30-Jan-2004  16:29  2000.80.911.0     180,792  Sqlmap70.dll     
   30-Jan-2004  16:29  2000.80.911.0      57,920  Sqlrepss.dll     
   30-Jan-2004  16:29  2000.80.911.0   7,610,449  Sqlservr.exe     
   30-Jan-2004  16:29  2000.80.911.0     590,396  Sqlsort.dll      
   30-Jan-2004  16:29  2000.80.911.0      45,644  Sqlvdi.dll       
   30-Jan-2004  16:29  2000.80.911.0     106,588  Sqsrvres.dll     
   30-Jan-2004  16:29  2000.80.911.0      33,340  Ssmslpcn.dll     
   30-Jan-2004  16:29  2000.80.911.0      82,492  Ssnetlib.dll     
   30-Jan-2004  16:29  2000.80.911.0      25,148  Ssnmpn70.dll     
   30-Jan-2004  16:29  2000.80.911.0     158,240  Svrnetcn.dll     
   30-Jan-2004  16:29  2000.80.911.0      76,416  Svrnetcn.exe     
   30-Jan-2004  16:29  2000.80.911.0      98,872  Xpweb70.dll      
   29-Jan-2004  23:24  2000.80.911.0     159,813  Replres.rll
   29-Jan-2004  23:17  2000.80.911.0      28,672  Sqlevn70.rll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Back to the top

STATUS

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.
Back to the top

MORE INFORMATION

To resolve this problem, you must turn on trace flag 9050 after you install the hotfix in the "Resolution" section. To do so, follow these steps:
  1. Start SQL Server Enterprise Manager.
  2. Right-click the instance of SQL Server, and then click Properties.
  3. Click the General tab, and then click Startup Parameters.
  4. In the Startup Parameters dialog box, type -T9050 in the Parameter box.
  5. Click Add, and then click OK.
  6. In the SQL Server Properties (Configure) dialog box, click OK.
  7. Restart the instance of SQL Server.
Additionally, you must turn on trace flag 9209. To turn on trace flag 9209, repeat the previous steps. However, in step 4, type -T9209 instead of -T9050 in the Parameter box. Trace flag 9209 is described in the following Microsoft Knowledge Base article:
830887  (http://support.microsoft.com/kb/830887/ ) FIX: Some queries that have a left outer join and an IS NULL filter run slower after you install SQL Server 2000 post-SP3 hotfix
Back to the top

REFERENCES

For more information about compile time, parse time, and execute time, visit the following Microsoft Web sites:
http://msdn2.microsoft.com/en-us/library/aa259194(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa259194(SQL.80).aspx)
http://msdn2.microsoft.com/en-us/library/aa173933(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa173933(SQL.80).aspx)
http://msdn2.microsoft.com/en-us/library/aa178303(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa178303(SQL.80).aspx)
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
263889  (http://support.microsoft.com/kb/263889/ ) SQL blocking due to [[COMPILE]] locks
243588  (http://support.microsoft.com/kb/243588/ ) How to troubleshoot the performance of ad-hoc queries
Back to the top
APPLIES TO
  • Microsoft SQL Server 2000 Service Pack 3
Back to the top
Keywords: 
kbhotfixserver kbqfe kbqfe kbquery kbsqlserv2000presp4fix kbfix kbbug KB836136
Back to the top