Intra-query parallelism bug fix for SQL Server 2000 SP4?

Hello,
We are running SQL Server 2000 SP4 on a server with dual-core CPU.
Recently we have noticed the following error message:
"Intra-query parallelism caused your server command (process ID #52) to
deadlock. Rerun the query ..."
I wonder if there is a fix available for that problem.
Thanks.You could try adding OPTION (MAXDOP 1) to the offending query.
Aaron Bertrand
SQL Server MVP
"miline" <miline@.discussions.microsoft.com> wrote in message
news:E8AAEB66-94B8-4A9E-BC5D-49EC773543B1@.microsoft.com...
> Hello,
> We are running SQL Server 2000 SP4 on a server with dual-core CPU.
> Recently we have noticed the following error message:
> "Intra-query parallelism caused your server command (process ID #52) to
> deadlock. Rerun the query ..."
> I wonder if there is a fix available for that problem.
> Thanks.
>|||Thank you for response.
Unfortunately I can not modify the application query. I can disable
parallelism for the whole server but that can decrease performance of the
production server. I am specifically looking for a fix from Microsoft if it
is available.
Regards,
"Aaron Bertrand [SQL Server MVP]" wrote:

> You could try adding OPTION (MAXDOP 1) to the offending query.
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "miline" <miline@.discussions.microsoft.com> wrote in message
> news:E8AAEB66-94B8-4A9E-BC5D-49EC773543B1@.microsoft.com...
>
>|||> Unfortunately I can not modify the application query. I can disable
> parallelism for the whole server but that can decrease performance of the
> production server. I am specifically looking for a fix from Microsoft if
> it
> is available.
Some other workarounds here:
http://support.microsoft.com/kb/837983
Also see
http://support.microsoft.com/kb/317821
(Just don't try to follow the three KB articles mentioned at the bottom;
they've all been pulled.)
Aaron Bertrand
SQL Server MVP
[vbcol=seagreen]
> Regards,
> "Aaron Bertrand [SQL Server MVP]" wrote:
>|||Thanks. I already saw that.
According to it, the only remaining option would be "enable the pre-SQL
Server 2000 SP3 parallel scan behavior" by setting trace flag 683 on (I woul
d
not like to disable multi-processor support unless very necessary). It is no
t
quite clear what does it mean "pre-SQL Server 2000 SP3"; I do have SQL Serve
r
2000 SP4. And the trace flag 683 is not mentioned in BOL, not sure if it wil
l
help with SP4. That error message does not appear very often; I can not test
it immediatelly.
Regards,
"Aaron Bertrand [SQL Server MVP]" wrote:

> Some other workarounds here:
> http://support.microsoft.com/kb/837983
> Also see
> http://support.microsoft.com/kb/317821
> (Just don't try to follow the three KB articles mentioned at the bottom;
> they've all been pulled.)
> --
> Aaron Bertrand
> SQL Server MVP
>
>
>
>
>|||> Also see
> http://support.microsoft.com/kb/317821
> (Just don't try to follow the three KB articles mentioned at the bottom;
> they've all been pulled.)
Actually the URLs were just broken due to a misplaced space. The article
will be corrected shortly.|||Thanks.
It is similar, they recommend to supress parallel execution as a workaround
there.
Regards,
"Aaron Bertrand [SQL Server MVP]" wrote:

> Actually the URLs were just broken due to a misplaced space. The article
> will be corrected shortly.
>
>