如果您有复杂的报告要求。需要大量 CPU 周期来构建的计算成本较高的报告（瓶颈：客户的 Celeron）、需要大量数据来构建的简单报告（瓶颈：客户的 ADSL）或介于两者之间的任何报告都属于此类。在功能强大的服务器上进行所有处理，然后将结果返回给客户端是有意义的。
如果您希望轻松管理独立于应用程序版本的报告。我帮助维护一个应用程序，该应用程序在每个版本中都分发了应用程序和报告。因为新版本通常是一件大事，所以我们尽可能避免它们。这意味着，如果应用程序不需要维护，我们可以在发布之间间隔 3 个月。这意味着对报告的小修复不会尽快推送给客户。新报告也是如此（客户喜欢新报告）。如果一切都通过 SSRS 控制，我们可以根据需要添加/编辑/删除报告。
后一种用例需要随时访问 SSRS 才有意义，它可能最适合多租户应用程序。
Is there any point in using SSRS to host your reports if you are only going to have one application using your SQL Server?
Yes.
I would have thought SSRS makes sense only if you are going to host reports that are going to be consumed by several separate applications.
I can think of two use cases for SSRS deployments for single applications (although I'm sure there are more):
If you have complex reporting requirements. Computationally expensive reports that require lots of CPU cycles to construct (bottleneck: Client's Celeron), simple reports that require lots of data to build (bottleneck: Client's ADSL), or anything in between will fall in to this category. It makes sense to do all the processing on powerful servers, and then render the result back to the client.
If you want easy management of reports separate to application releases. I help maintain an application which has both the application and reports distributed in each release. Because new releases are typically a big deal, we avoid them where possible. This means that if there's no maintenance required in the application, we can go 3 months between releases. This means small fixes to reports aren't pushed out to clients as fast as possible. Same goes for new reports (clients love new reports). If everything was controlled via SSRS, we could add/edit/remove reports as required.
The latter use case requires readily available access to SSRS to make sense, it's probably best suited to multi-tenant applications.
发布评论
评论（1）
是的。
我可以想到针对单个应用程序进行 SSRS 部署的两个用例（尽管我确信还有更多）：
如果您有复杂的报告要求。需要大量 CPU 周期来构建的计算成本较高的报告（瓶颈：客户的 Celeron）、需要大量数据来构建的简单报告（瓶颈：客户的 ADSL）或介于两者之间的任何报告都属于此类。在功能强大的服务器上进行所有处理，然后将结果返回给客户端是有意义的。
如果您希望轻松管理独立于应用程序版本的报告。我帮助维护一个应用程序，该应用程序在每个版本中都分发了应用程序和报告。因为新版本通常是一件大事，所以我们尽可能避免它们。这意味着，如果应用程序不需要维护，我们可以在发布之间间隔 3 个月。这意味着对报告的小修复不会尽快推送给客户。新报告也是如此（客户喜欢新报告）。如果一切都通过 SSRS 控制，我们可以根据需要添加/编辑/删除报告。
后一种用例需要随时访问 SSRS 才有意义，它可能最适合多租户应用程序。
Yes.
I can think of two use cases for SSRS deployments for single applications (although I'm sure there are more):
If you have complex reporting requirements. Computationally expensive reports that require lots of CPU cycles to construct (bottleneck: Client's Celeron), simple reports that require lots of data to build (bottleneck: Client's ADSL), or anything in between will fall in to this category. It makes sense to do all the processing on powerful servers, and then render the result back to the client.
If you want easy management of reports separate to application releases. I help maintain an application which has both the application and reports distributed in each release. Because new releases are typically a big deal, we avoid them where possible. This means that if there's no maintenance required in the application, we can go 3 months between releases. This means small fixes to reports aren't pushed out to clients as fast as possible. Same goes for new reports (clients love new reports). If everything was controlled via SSRS, we could add/edit/remove reports as required.
The latter use case requires readily available access to SSRS to make sense, it's probably best suited to multi-tenant applications.