Microsoft KB Archive/161726: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 76: | Line 76: | ||
Change the statement to:<br /> | Change the statement to:<br /> | ||
<pre class="codesample"> exec( | <pre class="codesample"> exec("select * from view") | ||
</pre> | </pre> | ||
<br /> | <br /> |
Latest revision as of 11:00, 21 July 2020
Article ID: 161726
Article Last Modified on 10/3/2003
APPLIES TO
- Microsoft SQL Server 6.5 Service Pack 2
This article was previously published under Q161726
BUG #: 16361 (Windows NT: 6.5)
SYMPTOMS
You may receive a handled access violation (AV) when you attempt to select from a view that was created with a DISTINCT clause, and there is a natural JOIN between base tables inside a stored procedure.
When the access violation occurs, you may find the following error message in the SQL Server errorlog:
WORKAROUND
To work around this problem, place the SELECT statement of the stored procedure inside an EXEC() statement.
For example, if the SELECT against the view was the following:
select * from view
Change the statement to:
exec("select * from view")
Otherwise, move the query outside of the stored procedure, or avoid using the DISTINCT keyword in the view definition.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5 Service Pack 1 and 2. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.
Additional query words: SP1 SP2
Keywords: kbbug kbfix kbusage KB161726