Microsoft KB Archive/175097

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:38, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Article ID: 175097

Article Last Modified on 10/16/2003



APPLIES TO

  • Microsoft SQL Server 6.5 Service Pack 3



This article was previously published under Q175097

BUG #: 16803 (6.5)

SYMPTOMS

If you run a query on a view defined with a subquery in its select list, you may experience impaired performance. However, a direct query for the equivalent select with no view (with or without a predicate against the view) yields much faster performance.

WORKAROUND

To resolve this problem, obtain and install the latest Service Pack for SQL Server 6.5. For more information, see the STATUS section of this article.

NOTE: To use the fix in the latest Service Pack, you must re-create the view with trace flag 349 enabled. For additional information, see the MORE INFORMATION section of this article.

To work around this problem and improve performance, do either of the following:

  • Execute the query on the underlying tables rather than on the view.


-or-

  • Create the view so that it does not contain a subquery for the select list.

NOTE: Views created under versions of SQL Server earlier than 6.5 Service Pack 1 with a subquery in the select list will continue to work, even under SQL Server 6.5 Service Pack 1 and later, provided that they are not re-created under these later versions of SQL Server.


STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5 Service Packs 1, 2, and 3. This problem was corrected in the latest Microsoft SQL Server 6.5 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

MORE INFORMATION

To use the fix for this bug, you must enable trace flag 349 (which was newly added). To ensure that the proper queries take advantage of this fix, you may consider starting the server with the trace flag enabled, so that all connections have the trace flag enabled. The SQL Server Setup program (in Server Options) provides a means to add startup parameters. Add the parameter -T349 to the list. You can enable the trace flag for a specific connection by executing DBCC TRACEON(349). Doing this is required to re-create the views(s) in question to invoke the new behavior.


Additional query words: sp sp1 sp2 sp3

Keywords: kbbug kbfix kbsqlserv650sp2bug kbusage kbsqlserv650sp3bug KB175097