0

目标:
在报表Service 2008 R2中根据下图显示结果。

问题:
我应该怎么做?

您还必须记住,实际上该列表包含大量数据,可能是 miljon

在此处输入图像描述 在此处输入图像描述

4

2 回答 2

0

我会使用一个带有文本框的列表来进行这种显示。此外,您可以考虑在每个客户之后添加分页符。

我个人在处理数千行时遇到了很多性能问题,更不用说数百万行了。

我对您的建议是重新考虑报告的主要目标:如果报告是用于导出目的 - 那么不要为此使用 ssrs。如果报告用于查看 - 那么也许可以使用每个用户选择的参数来缩小数据范围。

最后一件事,祝你好运:)

于 2013-01-20T07:28:55.677 回答
0

In terms of the report itself, this should be a fairly standard implementation.

You'll need to create one Tablix, with one Group for Customer (one row), one Group for Artist (two rows, one for the headers and one for the Artist name, then a detail row for the Title.

It looks like you need more formatting options for the Customers Textbox - you could merge the cells in the Customer header row, then insert a Rectangle, which will give you more options to move objects around in the row.

For large reports you've got a few options:

Processing large reports: http://msdn.microsoft.com/en-us/library/ms159638(v=sql.105).aspx

Report Snapshots: http://msdn.microsoft.com/en-us/library/ms156325(v=sql.105).aspx

Report Caching: http://msdn.microsoft.com/en-us/library/ms155927(v=sql.105).aspx

I would recommend scheduling a Snapshot overnight to offload the processing to a quiet time, then making sure the report has sensible pagination set up so not too much data has to be handled at one time when viewed (i.e. not trying to view thousands of reports at one time when viewed in Report Manager).

Another option would be to set up an overnight Subscription that could save the report to a fileshare or send it as an email.

Basically you're thinking about reducing the amount of processing that needs to be done at peak times and processing the report once for future use to reduce overall resource usage.

于 2013-01-19T22:31:44.050 回答