SQL Reporting Services 2008 与 Crystal Reports 相比?

发布于 2024-09-10 12:09:58 字数 651 浏览 2 评论 0原文

我正在决定是使用 SSRS 还是 CR 来满足我们的报告需求。我阅读了一些讨论,包括 Crystal Reports 与 Microsoft SQL Server Reporting服务比较 SQL Server Reporting Services 与 Crystal Reports。所有的观点都非常好且有效。

总体共识似乎是 SSRS 是更好的选择,特别是对于具有多种导出类型功能的基于 Web 的报告(C#、ASP.Net)。

我们在讨论中唯一担心的是,我们并不完全确定 SSRS 将如何破坏我们的 SQL Server。

另外,所有数据只能通过存储过程访问 - 不能直接访问表,而且我读过一些 CR 的 SQL 相关问题,这似乎是另一个阻碍。

我只是想确保在我们的生产服务器上使用 SSRS 不会以任何方式影响我们当前服务器的性能。

I'm in the process of deciding whether to use SSRS or CR for our reporting needs. I have read through several discussions, including Crystal Reports vs. Microsoft SQL Server Reporting Services and Compare SQL Server Reporting Services to Crystal Reports. All very good and valid points.

The over-all consensus seems to be that SSRS is a better bet, especially for web-based reporting (C#, ASP.Net) with multiple export type functionalities.

The only concern that we have had in discussions is that we're not entirely sure about how SSRS will gunk up our SQL Server.

Also, all of data is only accessible by sprocs - no direct table access, and I've read about some of CR's SQL-related issues, which appear to be yet another deterrent.

I just want to ensure that using SSRS on our productions servers will not in any way hinder our current server's performance.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

奢华的一滴泪 2024-09-17 12:09:58

SSRS 有一个非常好的缓存选项,因此它不会妨碍您的生产服务器。
CR 也有缓存,但它使用 ASP.NET 缓存(报告数据缓存在您的 Web 服务器工作进程中,我不推荐这样做)。

在我看来,SSRS 已经把 CR 打败了;我发现 SSRS IDE 比 CR 更容易使用,似乎更容易部署,而且 SSRS 提供了很多 CR 没有的选项。

我已经在 SSRS 和 CR 中使用了存储过程 - 我没有发现任何问题。

SSRS has a pretty good caching option, so it shouldn't hinder your production server.
CR has caching too, but it uses ASP.NET caching (the report data is cached in your web servers worker process and is not something I would recommend).

SSRS has blown CR away in my opinion; I find the SSRS IDE much easier to use than CR, it seems to be a lot easier to deploy, and SSRS offers a lot of options that CR doesn't.

I've used sprocs with both SSRS and CR - I haven't seen any issues with either.

伏妖词 2024-09-17 12:09:58

我们正在将 Crystal Enterprise 系统迁移到 SQL Reporting Services。经过一些研究和阅读,我发现 SSRS 易于使用和掌握。它有助于让您自己组织起来并决定您想要向用户呈现报告的安全结构。一旦我组织并发布了它,我决定采用我们拥有的最大、最复杂的 Crystal Report,并使用 SSRS 重新设计它(不使用任何 RPT 到 XML 工具)。这项任务帮助我学习了这种制作报告的新方法,我发现在 VS(或 Microsoft SQL Server Report Builder)中进行设计的能力非常简单,而且灵活性令人惊叹。

如果可以的话,我强烈建议您切换!

We are in the middle of a migration of our Crystal Enterprise system to SQL Reporting Services. After some research and a few reads, I'm finding SSRS easy to use and grasp. It helps to get yourself organized and decide on the security structure in which you want to present reports to your users. Once I had that organized and published, I decided to take the largest and most complex Crystal Report we have and re-design it using SSRS (not using any RPT to XML tool). This task has helped me learn this new way of doing reports and I find the ability to design in VS (or Microsoft SQL Server Report Builder) easy and the flexibilty amazing.

I highly recommend switching if you can!

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文