BUG: Parallel Query Generates Access Violation from Derived Table Populated from NULL Parameters (257564)
The information in this article applies to:
This article was previously published under Q257564
BUG #: 57654 (SQLBUG_70)
SYMPTOMS
If your query involves derived tables, it may terminate unexpectedly from an Access Violation (AV) if all of the following conditions are true:
- The query executes in a parallel plan.
- The query uses hash joins.
- One or more of the derived table values is a NULL value.
- The query uses a UNION to aggregate more than one row into the derived table.
WORKAROUND
To work around this problem, eliminate any one of the criteria listed in the "Symptoms" section. For example:
- Change the max degree of parallelism option to 1 by using the sp_configure stored procedure or add the (MAXDOP = 1) query hint to the query.
- Force a different type of join.
- Eliminate NULLS.
- Do not use UNIONs to aggregate results inside the derived table.
- Rewrite the query and use temporary tables rather than derived tables.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0.
Modification Type: | Major | Last Reviewed: | 10/16/2002 |
---|
Keywords: | kbBug KB257564 |
---|
|