Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
bassist695
Starting Member
9 Posts |
Posted - 2005-04-13 : 10:58:37
|
I'm on a data warehouse team, and have been getting many requests for reports consisting of large sets of data (in excess of 1000 rows). Many are unmanageably large when it comes to usefully rendering a report, resulting in hundreds of pages.What is the best way to go about (1) cutting down on the data size in an acceptable manner, and/or (2) cutting down on the sheer length of these reports? In practice, what is the upper limit of a dataset that Reporting Services can work with?Thanks for your advice.Mike |
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2005-04-13 : 12:53:55
|
Are you familiar with grouping and aggregating data? i.e., instead of 1 row per transaction, you return totals per Customer or totals per month or something like that. It's up to the client to tell you what level of detail they want in the report -- they may very well want 100 pages if they need the detail. But often they are not aware that you can provide summaries to them, in which case if it is on-line they can drill into the details, or they can run a separate "Detail" report that perhaps has parameters to let them narrow their criteria ... (i.e., in my previous example, perhaps they can pick a particular Customer).- Jeff |
 |
|
jhermiz
3564 Posts |
Posted - 2005-04-13 : 13:07:26
|
you may also want to flip the size properties of the report and do a landscape report if you have a lot of text details. You will save paper since the text or notes fields will have more room to take up on a landscape vs. portrait view. Otherwise the only other way to reduce the number of rows is to allow the end user to filter the data. Keeping the web experience alive -- [url]http://www.web-impulse.com[/url]Imperfection living for perfection -- [url]http://jhermiz.blogspot.com/[/url] |
 |
|
|
|
|