Hilary Cotter mentioned to someone to reapply SP3A to fix the problem.
I have a really stupid question. Which device are you reapplying
SP3A? (The distributor, publisher, and or clients?)
Thanks,
Amy M
subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Amy M" <amarshall@.rhtc.net> wrote in message
news:119d3885.0410110449.5b71bed@.posting.google.co m...
> Hilary Cotter mentioned to someone to reapply SP3A to fix the problem.
> I have a really stupid question. Which device are you reapplying
> SP3A? (The distributor, publisher, and or clients?)
> Thanks,
> Amy M
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:<O3FbtBFsEHA.1272@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> subscriber.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Amy M" <amarshall@.rhtc.net> wrote in message
> news:119d3885.0410110449.5b71bed@.posting.google.co m...
Hilary,
I've reapplied to the subscriber, with no luck. The only way to clear
it out is to reinitialize the subscription. That works for some users
who don't input a lot of data, but for users who do input large
amounts of data, their data would be lost.
Any more suggestions? (The subscriber OS is WinXP, sp2)
Showing posts with label fix. Show all posts
Showing posts with label fix. Show all posts
Monday, March 19, 2012
Invalid Cursor State
All,
SQL 2000 sp3 hotfix 871, Server 2000 sp4
Any hotfix greater than 859 will have this problem. The fix is to get hotfix
876, kb article 831997 is the one you want to tell them to reference. Its f
ree.
Gary Abbott Super DBA, lolThat KB article isn't public, FYI. 878 is (see http://www.aspfaq.com/2515).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:74016FAB-0BBF-4FB8-88C0-4CA6A448E68B@.microsoft.com...
> All,
> SQL 2000 sp3 hotfix 871, Server 2000 sp4
> Any hotfix greater than 859 will have this problem. The fix is to get
hotfix 876, kb article 831997 is the one you want to tell them to reference.
Its free.
> Gary Abbott Super DBA, lol|||They wouldn't give me 878, I did ask. Reading one of your earlier posts.|||Did they give you a reason? How did you come across 876?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:BB74A25F-6B90-44CA-9177-F67574DFC2EF@.microsoft.com...
> They wouldn't give me 878, I did ask. Reading one of your earlier posts.
SQL 2000 sp3 hotfix 871, Server 2000 sp4
Any hotfix greater than 859 will have this problem. The fix is to get hotfix
876, kb article 831997 is the one you want to tell them to reference. Its f
ree.
Gary Abbott Super DBA, lolThat KB article isn't public, FYI. 878 is (see http://www.aspfaq.com/2515).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:74016FAB-0BBF-4FB8-88C0-4CA6A448E68B@.microsoft.com...
> All,
> SQL 2000 sp3 hotfix 871, Server 2000 sp4
> Any hotfix greater than 859 will have this problem. The fix is to get
hotfix 876, kb article 831997 is the one you want to tell them to reference.
Its free.
> Gary Abbott Super DBA, lol|||They wouldn't give me 878, I did ask. Reading one of your earlier posts.|||Did they give you a reason? How did you come across 876?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:BB74A25F-6B90-44CA-9177-F67574DFC2EF@.microsoft.com...
> They wouldn't give me 878, I did ask. Reading one of your earlier posts.
Friday, March 9, 2012
Invalid buffer received from client..
Invalid buffer received from client..
Error: 17805, Severity: 20, State: 3
Anybody else has this? Any rumors about a fix to it?I know SQL SP3 has added a bunch of new error messages for things we were all blissfully unaware of before. This looks like one of them. If this is taking your server down, you can look into the fix on KB article 818897.|||That's where I started, but realized that this patch eliminates the AV, not the fact that the proc will fail anyway and the error will sill post.
I found a similar issue raised in ms sqlserver news group, where they had a declaration discrepancy between a passed NVARCHAR param and param definition in the proc (VARCHAR). Once they mirrored the definitions the error disappeared. In our case there is nothing to change, on both sides the parm declared as TEXT (or so my developers say it is on FE). Of course, I'll make sure they're not "exagerating" :), but the fact stays for now, - TEXT = TEXT.
Error: 17805, Severity: 20, State: 3
Anybody else has this? Any rumors about a fix to it?I know SQL SP3 has added a bunch of new error messages for things we were all blissfully unaware of before. This looks like one of them. If this is taking your server down, you can look into the fix on KB article 818897.|||That's where I started, but realized that this patch eliminates the AV, not the fact that the proc will fail anyway and the error will sill post.
I found a similar issue raised in ms sqlserver news group, where they had a declaration discrepancy between a passed NVARCHAR param and param definition in the proc (VARCHAR). Once they mirrored the definitions the error disappeared. In our case there is nothing to change, on both sides the parm declared as TEXT (or so my developers say it is on FE). Of course, I'll make sure they're not "exagerating" :), but the fact stays for now, - TEXT = TEXT.
Wednesday, March 7, 2012
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...
> > 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.
> >
>
>|||> 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
> 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...
>> > 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.
>> >
>>|||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 would
not like to disable multi-processor support unless very necessary). It is not
quite clear what does it mean "pre-SQL Server 2000 SP3"; I do have SQL Server
2000 SP4. And the trace flag 683 is not mentioned in BOL, not sure if it will
help with SP4. That error message does not appear very often; I can not test
it immediatelly.
Regards,
"Aaron Bertrand [SQL Server MVP]" wrote:
> > 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
>
>
>
> >
> > 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...
> >> > 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.
> >> >
> >>
> >>
> >>
>
>|||> 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:
> > 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.
>
>
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...
> > 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.
> >
>
>|||> 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
> 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...
>> > 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.
>> >
>>|||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 would
not like to disable multi-processor support unless very necessary). It is not
quite clear what does it mean "pre-SQL Server 2000 SP3"; I do have SQL Server
2000 SP4. And the trace flag 683 is not mentioned in BOL, not sure if it will
help with SP4. That error message does not appear very often; I can not test
it immediatelly.
Regards,
"Aaron Bertrand [SQL Server MVP]" wrote:
> > 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
>
>
>
> >
> > 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...
> >> > 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.
> >> >
> >>
> >>
> >>
>
>|||> 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:
> > 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.
>
>
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.
>
>
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.
>
>
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 would
not like to disable multi-processor support unless very necessary). It is not
quite clear what does it mean "pre-SQL Server 2000 SP3"; I do have SQL Server
2000 SP4. And the trace flag 683 is not mentioned in BOL, not sure if it will
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.
>
>
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 would
not like to disable multi-processor support unless very necessary). It is not
quite clear what does it mean "pre-SQL Server 2000 SP3"; I do have SQL Server
2000 SP4. And the trace flag 683 is not mentioned in BOL, not sure if it will
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.
>
>
Subscribe to:
Posts (Atom)