sql server 2005 - Should I use stored procedures for reports in SQL Reporting Services -


When I write a report for SQL reporting services, I put SQL-script inside my report (SDL). When I run this script in SQL Management Studio it takes about 1 second, but the report is generated for a long time (sometimes the report throws an exception about the timeout).

Should I write the stored procedure and use it in the report? Will it be faster?

And another question - when SQL-script returns to multiple rows, does the report get all the rows and only show one page, or does it take only one page from the SQL server?

Thanks in advance.

stored procs vs. ad-hoc / dynamic sql:

if the report is running Data is relatively unchanged, so you might want to consider caching:

I personally feel the favor because it is easy to reuse.

What's going on according to the RSE Execution Log / (or No!) To see how long the process is going to be done:


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -