FIX: Queries that join a view may run slowly if the view contains outer joins

Article translations Article translations
Article ID: 840406 - View products that this article applies to.
Bug #: 471308 (SHILOH_BUGS)
Expand all | Collapse all

On This Page

SYMPTOMS

If you have a query that joins a view, and the view contains outer joins, the query may run slowly.

CAUSE

This problem occurs because the Microsoft SQL Server query optimizer does not produce certain join orders that may be more efficient during the query plan optimization.

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 How to obtain the latest SQL Server 2000 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later) 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
   -------------------------------------------------------------------------
   31-May-2003  16:45  2000.80.818.0      78,400  Console.exe      
   25-Mar-2004  20:27  2000.80.928.0     315,968  Custtask.dll     
   30-Jan-2004  14:29  2000.80.911.0      33,340  Dbmslpcn.dll     
   25-Apr-2003  00:12                    786,432  Distmdl.ldf
   25-Apr-2003  00:12                  2,359,296  Distmdl.mdf
   29-Jan-2003  23:55                        180  Drop_repl_hotfix.sql
   12-Sep-2003  01:26  2000.80.859.0   1,905,216  Dtspkg.dll       
   26-Aug-2003  18:16  2000.80.854.0     528,960  Dtspump.dll      
   23-Jun-2003  20:40  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  20:40  2000.80.837.0     639,552  Dtswiz.dll       
   24-Apr-2003  00:51                    747,927  Instdist.sql
   02-May-2003  23:56                      1,581  Inst_repl_hotfix.sql
   30-Jan-2004  14:29  2000.80.911.0      90,692  Msgprox.dll      
   01-Apr-2003  00:07                      1,873  Odsole.sql
   30-Jan-2004  14:29  2000.80.911.0      62,024  Odsole70.dll     
   30-Jan-2004  14:29  2000.80.911.0      25,144  Opends60.dll     
   30-Jan-2004  14:29  2000.80.911.0      57,904  Osql.exe         
   02-Apr-2003  21:15  2000.80.797.0     279,104  Pfutil80.dll     
   04-Aug-2003  16:17                    550,780  Procsyst.sql
   11-Sep-2003  22:37                     12,305  Qfe469315.sql
   22-May-2003  20:57                     19,195  Qfe469571.sql
   25-Mar-2004  19:03                  1,104,848  Replmerg.sql
   30-Jan-2004  14:29  2000.80.911.0     221,768  Replprov.dll     
   30-Jan-2004  14:29  2000.80.911.0     307,784  Replrec.dll      
   29-Jan-2004  21:24  2000.80.911.0     159,813  Replres.rll
   05-Sep-2003  22:00                  1,087,150  Replsys.sql
   13-Aug-2003  14:28                    986,603  Repltran.sql
   30-Jan-2004  14:29  2000.80.911.0     287,304  Rinitcom.dll     
   25-Mar-2004  20:27  2000.80.928.0      66,112  Semmap.dll       
   30-Jan-2004  14:29  2000.80.911.0      57,916  Semnt.dll        
   29-Jul-2003  18:13  2000.80.819.0     492,096  Semobj.dll       
   31-May-2003  16:27  2000.80.818.0     172,032  Semobj.rll
   02-Jan-2004  17:42  2000.80.904.0      53,832  Snapshot.exe     
   09-Dec-2003  18:07                    117,834  Sp3_serv_uni.sql
   04-Feb-2004  22:46  2000.80.913.0      28,672  Sqlagent.dll     
   04-Feb-2004  22:47  2000.80.913.0     311,872  Sqlagent.exe     
   19-Feb-2004  16:02  2000.80.916.0     168,001  Sqlakw32.dll     
   12-Mar-2004  02:34  2000.80.923.0      33,344  Sqlctr80.dll     
   30-Jan-2004  14:29  2000.80.911.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  15:44                     25,172  Sqldumper.exe    
   29-Jan-2004  21:17  2000.80.911.0      28,672  Sqlevn70.rll
   05-Mar-2004  15:13  2000.80.922.0     180,792  Sqlmap70.dll     
   03-Sep-2003  00:56  2000.80.857.0     188,992  Sqlmmc.dll       
   02-Sep-2003  21:03  2000.80.857.0     479,232  Sqlmmc.rll
   21-Oct-2003  22:08  2000.80.871.0     401,984  Sqlqry.dll       
   30-Jan-2004  14:29  2000.80.911.0      57,920  Sqlrepss.dll     
   13-Apr-2004  17:31  2000.80.933.0   7,626,833  Sqlservr.exe     
   30-Jan-2004  14:29  2000.80.911.0     590,396  Sqlsort.dll      
   30-Jan-2004  14:29  2000.80.911.0      45,644  Sqlvdi.dll       
   30-Jan-2004  14:29  2000.80.911.0     106,588  Sqsrvres.dll     
   30-Jan-2004  14:29  2000.80.911.0      33,340  Ssmslpcn.dll     
   30-Jan-2004  14:29  2000.80.911.0      82,492  Ssnetlib.dll     
   30-Jan-2004  14:29  2000.80.911.0      25,148  Ssnmpn70.dll     
   28-Oct-2003  02:21  2000.80.873.0     123,456  Stardds.dll      
   30-Jan-2004  14:29  2000.80.911.0     158,240  Svrnetcn.dll     
   30-Jan-2004  14:29  2000.80.911.0      76,416  Svrnetcn.exe     
   30-Apr-2003  21:52  2000.80.816.0      45,132  Ums.dll          
   30-Jan-2004  14:29  2000.80.911.0      98,872  Xpweb70.dll      

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

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.

MORE INFORMATION

After you apply this hotfix, you must enable trace flag 9052 for the fix to take effect. To do this, 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 -T9052 in the Parameter box.
  5. Click Add, and then click OK.
  6. In the SQL Server Properties dialog box, click OK.
  7. Restart SQL Server.
Note You can also dynamically enable the trace flag by running the dbcc traceon(9052,-1) command. If you run this command, you do not have to restart SQL Server. However, you must run this command every time that you restart SQL Server.

Properties

Article ID: 840406 - Last Review: November 2, 2007 - Revision: 2.3
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
Keywords: 
kbsqlserv2000presp4fix kbfix kbbug kbhotfixserver kbqfe KB840406

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com