Doing a profiler on our sql box during the generation of a SQL reporting
service report, I noticed that three queries were taking place. We have
three datasets in our report. One is to get information for paramater A,
another for Parameter B and yet the final dataset which returns the
information used to populate the report. Each time the report is run, the
three queries are run, one for each dataset.
Is it possible to cache a dataset using reporting services or SQL or some
other means to reduce hits to the database while still getting the live data
from the third dataset which is used to populate the report?
I am aware of the cached reports which we plan to use, but is there a way to
just cache one dataset? Or two?
ThanksThis is a multi-part message in MIME format.
--=_NextPart_000_000D_01C622C8.CBF0B030
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Yes, ASP.NET 2.0 introduced a built-in cache invalidation mechanism =that can work with SQL Server 7.0 and above.
And it's easy to setup. Google aspnet_regsql for more information
However this caching mechanism is only supported at the table level for =SQL Server 7 and 2000
SQL Server 2005 has more invalidation possibilities
Med Bouchenafa
"isicoder" <isicoder@.newsgroups.nospam> a =E9crit dans le message de =news: u7Cr2YqIGHA.3000@.TK2MSFTNGP14.phx.gbl...
> Doing a profiler on our sql box during the generation of a SQL =reporting > service report, I noticed that three queries were taking place. We =have > three datasets in our report. One is to get information for paramater =A, > another for Parameter B and yet the final dataset which returns the > information used to populate the report. Each time the report is run, =the > three queries are run, one for each dataset.
> > Is it possible to cache a dataset using reporting services or SQL or =some > other means to reduce hits to the database while still getting the =live data > from the third dataset which is used to populate the report?
> > I am aware of the cached reports which we plan to use, but is there a =way to > just cache one dataset? Or two?
> > Thanks
> >
--=_NextPart_000_000D_01C622C8.CBF0B030
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Yes, ASP.NET 2.0 introduced a =built-in cache invalidation mechanism that can work with SQL Server 7.0 and =above.
And it's easy to setup. Google aspnet_regsql for more information
However this caching mechanism is only supported at the table level for SQL Server 7 and =2000
SQL Server 2005 has more invalidation possibilities
Med Bouchenafa
"isicoder" = a =E9crit dans le message de news: =u7Cr2YqIGHA.3000@.TK2MSFTNGP14.phx.gbl...> Doing a profiler on our sql box during the generation of a SQL reporting => service report, I noticed that three queries were taking =place. We have > three datasets in our report. One is to get =information for paramater A, > another for Parameter B and yet the final =dataset which returns the > information used to populate the =report. Each time the report is run, the > three queries are run, one for each =dataset.> > Is it possible to cache a dataset using =reporting services or SQL or some > other means to reduce hits to the =database while still getting the live data > from the third dataset which =is used to populate the report?> > I am aware of the cached =reports which we plan to use, but is there a way to > just cache one dataset? =Or two?> > Thanks> =>
--=_NextPart_000_000D_01C622C8.CBF0B030--
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment