FIX: Optimizer Chooses Table Scan Instead of Index Seek for Simple SELECT Involving @@identity

Article translations Article translations
Article ID: 246177 - View products that this article applies to.
This article was previously published under Q246177
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55626 (SQLBUG_70)
Expand all | Collapse all


When you include @@IDENTITY in the WHERE clause of a SELECT statement, the Query Optimizer chooses to perform a table scan rather than using the appropriate index.


@@IDENTITY is not being recognized as a run-time constant.


Declare a variable, set it equal to @@IDENTITY, and then use the variable in the SELECT statement.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 246177 - Last Review: October 22, 2013 - Revision: 2.1
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix KB246177

Contact us for more help

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