Saturday, February 25, 2012

Reporting server causes blocking on db server

I am seeing my reporing server (v2005) has a conneciton to my db server that
is causing blocking. the dbcc inputbuffer results show this: "
ReportServer.dbo.WriteLockSession;1 "
I dont see any entries on Google for this problem, does anyone know what the
RS server is doing? the thread appears to be hung.
thanks in advance!Its a long story but the default for Sql Server is read commited meaning it
will block updates while reading the data. you can add
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
To the beginning of your query in generic query mode. This will fix the
problem.
Carl Henthorn wrote:
>I am seeing my reporing server (v2005) has a conneciton to my db server that
>is causing blocking. the dbcc inputbuffer results show this: "
>ReportServer.dbo.WriteLockSession;1 "
>I dont see any entries on Google for this problem, does anyone know what the
>RS server is doing? the thread appears to be hung.
>thanks in advance!
--
Message posted via http://www.sqlmonster.com|||ReportServer is the database used by Reporting Services. It does not contain
any data that is being reported off of by a user. Unless he has some reports
that are query RS system tables then no reports or queries whatsoever by
anybody but RS is occuring.
My question is, what is the result to other activities? I have RS running on
my datamart and see no problems.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ghunter via SQLMonster.com" <u4529@.uwe> wrote in message
news:64f4e1087cea1@.uwe...
> Its a long story but the default for Sql Server is read commited meaning
> it
> will block updates while reading the data. you can add
> SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
> To the beginning of your query in generic query mode. This will fix the
> problem.
>
> Carl Henthorn wrote:
>>I am seeing my reporing server (v2005) has a conneciton to my db server
>>that
>>is causing blocking. the dbcc inputbuffer results show this: "
>>ReportServer.dbo.WriteLockSession;1 "
>>I dont see any entries on Google for this problem, does anyone know what
>>the
>>RS server is doing? the thread appears to be hung.
>>thanks in advance!
> --
> Message posted via http://www.sqlmonster.com
>|||While I dont have anything queryin ghte ReportServer db, I did have a report
querying another db on that server. As it turns out, another team added a
report that literally hundereds of users where using to check and download as
PDF convention agendas. This second report seems to have overwhelmed the
server and cuased this problem. For my report, i pointed it to a different
server and it now runs fine, and I havnt seen any blocking since.
thank you for your help!!
"Bruce L-C [MVP]" wrote:
> ReportServer is the database used by Reporting Services. It does not contain
> any data that is being reported off of by a user. Unless he has some reports
> that are query RS system tables then no reports or queries whatsoever by
> anybody but RS is occuring.
> My question is, what is the result to other activities? I have RS running on
> my datamart and see no problems.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ghunter via SQLMonster.com" <u4529@.uwe> wrote in message
> news:64f4e1087cea1@.uwe...
> > Its a long story but the default for Sql Server is read commited meaning
> > it
> > will block updates while reading the data. you can add
> >
> > SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
> >
> > To the beginning of your query in generic query mode. This will fix the
> > problem.
> >
> >
> > Carl Henthorn wrote:
> >>I am seeing my reporing server (v2005) has a conneciton to my db server
> >>that
> >>is causing blocking. the dbcc inputbuffer results show this: "
> >>ReportServer.dbo.WriteLockSession;1 "
> >>I dont see any entries on Google for this problem, does anyone know what
> >>the
> >>RS server is doing? the thread appears to be hung.
> >>thanks in advance!
> >
> > --
> > Message posted via http://www.sqlmonster.com
> >
>
>|||That makes sense. PDF is very intensive rendering operation.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Carl Henthorn" <CarlHenthorn@.discussions.microsoft.com> wrote in message
news:117C3B33-0E10-4F10-A7C9-F9ED8EBAE567@.microsoft.com...
> While I dont have anything queryin ghte ReportServer db, I did have a
> report
> querying another db on that server. As it turns out, another team added a
> report that literally hundereds of users where using to check and download
> as
> PDF convention agendas. This second report seems to have overwhelmed the
> server and cuased this problem. For my report, i pointed it to a different
> server and it now runs fine, and I havnt seen any blocking since.
> thank you for your help!!
> "Bruce L-C [MVP]" wrote:
>> ReportServer is the database used by Reporting Services. It does not
>> contain
>> any data that is being reported off of by a user. Unless he has some
>> reports
>> that are query RS system tables then no reports or queries whatsoever by
>> anybody but RS is occuring.
>> My question is, what is the result to other activities? I have RS running
>> on
>> my datamart and see no problems.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "ghunter via SQLMonster.com" <u4529@.uwe> wrote in message
>> news:64f4e1087cea1@.uwe...
>> > Its a long story but the default for Sql Server is read commited
>> > meaning
>> > it
>> > will block updates while reading the data. you can add
>> >
>> > SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
>> >
>> > To the beginning of your query in generic query mode. This will fix the
>> > problem.
>> >
>> >
>> > Carl Henthorn wrote:
>> >>I am seeing my reporing server (v2005) has a conneciton to my db server
>> >>that
>> >>is causing blocking. the dbcc inputbuffer results show this: "
>> >>ReportServer.dbo.WriteLockSession;1 "
>> >>I dont see any entries on Google for this problem, does anyone know
>> >>what
>> >>the
>> >>RS server is doing? the thread appears to be hung.
>> >>thanks in advance!
>> >
>> > --
>> > Message posted via http://www.sqlmonster.com
>> >
>>

No comments:

Post a Comment