FIX: SELECT Statement with Two LIKE Clauses Where the Table Has a CHECK Constraint Causes AV (284237)
The information in this article applies to:
This article was previously published under Q284237
BUG #: 57640 (SQLBUG_70)
SYMPTOMS
A SELECT statement may generate an access violation when all of the following conditions are true:
- A CHECK constraint exists on one of the columns in the table, and that column is used in the query.
- A composite nonclustered index exists on the table, and the order of the columns in the index is not the same as in the query.
- The query has at least two LIKE clauses in the WHERE condition.
WORKAROUND
One possible workaround is to replace a LIKE clause with an equality.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
| Modification Type: | Major | Last Reviewed: | 3/14/2006 |
|---|
| Keywords: | kbbug kbfix KB284237 |
|---|
|