BUG: SELECT DISTINCT Using Negative Int in WHERE Can Cause AVID: Q236443
|
A SELECT statement using DISTINCT that contains a large negative integer value in a condition of the WHERE clause can result in a handled access violation (AV).
The query will be terminated and an entry in the SQL Server error log will indicate the following:
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process spid generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
Version File name Platform
----------------------------------------
7.00.0703 S70703i.exe Intel
S70703a.exe Alpha
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.Q154871 Determining If You Are Eligible for No-Charge Technical Support
Microsoft has confirmed this to be a problem in SQL Server version 7.0.
The following is an example of a query that meets the condition of this problem:
select distinct employeeid from employees where employeeid = -2147482112
Additional query words: errorlog
Keywords : SSrvTran_SQL kbbug7.00
Version : winnt:7.0
Platform : winnt
Issue type : kbbug
Last Reviewed: July 6, 1999