Wednesday, March 28, 2012

Reporting Services seems to requery or refresh during drilldown

I have a report in reporting services with a single level of grouping:
Order
> Items
When I return the result the report is fine, but if I try to drill down into
an order, the screen flashes (as in a refresh), and then pushes the item I
opened to the top of the screen. It seems to be re-querying the database on
every click into the drilldown. Even though the result set is not large,
it's drawing it from a production database, and it takes several seconds to
complete the query.
Is it requerying, or is there a display issue? We're in the early stages of
using reporting services and it's currently running on an underpowered
machine for the server. Still, the result set has already been returned, and
shouldn't have to be drawn from the DB every time you drill down into a
single order.
Any ideas?I'm pretty sure it is a display issue. Just look at the HTML source code.
Every time you click into the drilldown, it does a postback to the server
and executing some "hide and show" code for the report.
The only time a query is send to the database is when you see the
"Generating Report" image.
"Ben Graham" <BenGraham@.discussions.microsoft.com> a écrit dans le message
de news:96761387-77EB-48C4-A40D-889ABD3521C9@.microsoft.com...
> I have a report in reporting services with a single level of grouping:
> Order
> > Items
> When I return the result the report is fine, but if I try to drill down
into
> an order, the screen flashes (as in a refresh), and then pushes the item I
> opened to the top of the screen. It seems to be re-querying the database
on
> every click into the drilldown. Even though the result set is not large,
> it's drawing it from a production database, and it takes several seconds
to
> complete the query.
> Is it requerying, or is there a display issue? We're in the early stages
of
> using reporting services and it's currently running on an underpowered
> machine for the server. Still, the result set has already been returned,
and
> shouldn't have to be drawn from the DB every time you drill down into a
> single order.
> Any ideas?
>

No comments:

Post a Comment