您选择的报告工具是什么？
每个项目都不可避免地需要某种类型的报告功能。 从您选择的语言中的 foreach 循环到全面的 BI 平台。
为了完成工作，该团队使用了哪些工具、小部件、平台，取得了成功、挫折和失败？
Every project invariably needs some type of reporting functionality. From a foreach loop in your language of choice to a full blow BI platform.
To get the job done what tools, widgets, platforms has the group used with success, frustration and failure?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（23）
我不得不承认，我真的很喜欢 SQL Server Reporting Services。 它只是做事，而且很容易做。
I would have to agree, I really like SQL Server Reporting Services. It just does stuff, and does it easily.
对于大多数报告，我们使用 BIRT。
For most reports we use BIRT.
对于制作相当“普通”的报告来说，SQL Reporting Services 确实令人印象深刻。
对于复杂的分析，将数据（可能是预先聚合的）加载到 Excel 数据透视表中通常对于大多数用户来说就足够了。
我发现您可以花费大量时间（和金钱）构建一个全面的“临时”报告套件，并且在“令人惊叹的因素”的第一个月或两个月之后，生成的 99％ 的报告将与以下内容相同：一组固定参数的微小差异。
当用户说他们想要“临时”报告而不指定他们寻找的目标时，不要接受。 他们只是在钓鱼，他们实际上需要花费与构建他们的解决方案一样多的时间来思考他们的报告要求。
我花了太多时间构建“可以报告一切的系统”，但在完成之前它就已经过时或失宠了。 最好尽快获得快速胜利，然后花时间“系统化”最重要的报告。
For knocking out fairly "run of the mill" reports, SQL Reporting Services is really quite impressive.
For complicated analysis, loading the data (maybe pre-aggregated) into an Excel Pivot table is usually adequate for most users.
I've found you can spend a lot of time (and money) building a comprehensive "ad-hoc" reporting suite and after the first month or two of "wow factor", 99% of the reports generated will be the same report with minor differences in a fixed set of parameters.
Don't accept when a user says they want "ad-hoc" reports without specifying what goals and targets their looking for. They are just fishing and they need to actually spend as much time on THINKING about THEIR reporting requirements as YOU would have to spend BUILDING their solution.
I've spent too much time building the "the system that can report everything" and for it to become out of date or out of favour before it was finished. Much better to get the quick wins out of the way as quick as possible and then spend time "systemising" the most important reports.
我是 BIRT 项目的提交者，所以我有偏见。 BIRT 为所需的各种设计和部署功能提供了经过深思熟虑的报告对象模型 (ROM) 和适当的 API。 此外，BIRT 提供了最好的多语言支持以及通过使用 CSS 将开发与设计分离的能力。
BIRT 可以通过 REAPI 嵌入到您的应用程序中，无需支付许可费用，也可以通过一些商业产品购买。
I am a committer on the BIRT project, so I am biased. BIRT provides a very well thought out report object model (ROM) and appropriate API for the various design and deploy function that is needed. In addition, BIRT provides the best multi-language support and the ability to separate development from design through the use of CSS.
BIRT can be embedded into your application for no license cost through the REAPI or it can be purchased through a couple of commercial offerings.
对于很多项目，我们使用 ActiveReports。
For a lot of projects we use ActiveReports.
我已经相当广泛地使用了 Reporting Services 和 Crystal，目前我正在使用 Excel(ick) 编写一些报告。
Reporting Services 对于简单的报告来说相当不错，但一旦您需要完全控制格式、复杂的公式和图表等，Crystal 就遥遥领先。 我还发现 Crystal 更有用； 能够在报告预览中更改内容是非常宝贵的（在 RS 的更高版本中可能有可能吗？）。
RS 还需要部署到 Web 服务器，如果您正在编写需要外部部署的应用程序，这会限制它的实用性。
旧版本的 Crystal 有很多错误，但最新版本要好得多，它比 Reporting Services 成熟得多。
I've used Reporting Services and Crystal fairly extensively, and I'm writing a few reports using Excel(ick) at the moment.
Reporting Services is pretty good for simple reports but as soon as you need total control over formatting,complex formulas and charts etc. Crystal is a long way ahead. I also find Crystal to be far more usable; being able to change things within the report preview is invaluable (it may be possible in later versions of RS?).
RS also needs to be deployed to a web server which limits it's usefulness if you are writing applications that need to be deployed externally.
Older versions of Crystal were very buggy but the latest ones are much better, it's much more mature than Reporting Services.
我们使用 i-net Clear Reports 进行报告（请参阅就像我们如何“吃自己的狗粮”）。 ;)
We use i-net Clear Reports for our reporting (seeing as how we "eat our own dog food"). ;)
Cognos 是一套强大的工具（我们将其用作 Oracle 后端的前端），但明显缺乏有关如何完成复杂报告任务的文档 - 大多数情况下，您最终都会敲打它，直到您了解如何完成复杂的报告任务。找点事做。
我不会低估使用 Microsoft Access 作为报告前端的有用性。 它没有那么有用的网络功能，但对于内部报告来说，它的用途非常广泛，而且功能强大得令人惊讶。
Cognos is a robust suite of tools (we use it as a front-end for an Oracle back-end), but there's a pronounced lack of documentation on how to accomplish complex reporting tasks -- mostly, you end up banging on it until you get something to work.
I wouldn't discount the usefulness of using Microsoft Access as a reporting front-end. It doesn't have that useful Web-enabled functionality, but for in-house reports it's very versatile and surprisingly powerful.
我确实没有太多 SSAS 工作要做，但我对此很感兴趣：
Cube ASP.net 浏览器
它在 Web 应用程序中提供了 Excel 数据透视表的许多功能（我认为我不是 Excel 方面的专家，无法真正了解数据透视表的全部功能 - 它位于至少看起来与 Visual Studio 的立方体浏览器相当）。
不幸的是，演示似乎不再在线:(
I don't really have much SSAS work to do but I've been quite taken with this:
Cube Browser for ASP.net
It offers many of the capabilities of an excel pivot table in a web app, (thought I'm not enough of an expert on Excel to really know the whole of the pivot table's capabilities - it at least looks comparable to visual studio's cube browser).
Unfortunately the demos don't seem to be online anymore :(
如果您拥有世界上所有的钱，请选择 Cognos。 他们提供了一个数据立方体，本质上使报告“无需开发人员”，最终用户可以创建报告、仪表板以及他们喜欢的任何内容。
对于“普通人”来说，我非常喜欢 .NET 库/工具的 ComponentOne 报告。 它与 Crystal Reports 有类似的感觉，但具有非常友好的 XML 格式，您可以在后台进行编辑，并且不会出现版本控制、密钥以及我在对其中任何一个进行简单更新时必须处理的其他项目的麻烦。报告或基础版本。
If you have all the money in the world, go with Cognos. They provide a data cube that essentially makes the reporting "developer free" and the end user can create reports, dashboards, anything they like.
For the "common man", I've grown quite fond of the ComponentOne reports for .NET library/tools. It has a similar feel to Crystal Reports, but has a very friendly XML format that you and edit under the hood and none of the headaches with versioning, keys, and other items that I've had to deal with when making simple updates to either the report or the underlying version.
Crystal Reports，因为很容易获取完全相同的报告文件，并且
1 - 将其发布到 Intranet 上
2 - 将其嵌入到应用程序中
3 - 定期将其作为 Excel 输出通过电子邮件发送给需要它的任何人
另外（如我已经建议过），它可以轻松导出为 Excel、PDF 和其他格式。
Crystal Reports, because it is easy to take the same exact report file and
1 - Post it on the intranet
2 - Embed it in an application
3 - Schedule it to be emailed as an Excel output every so often to whoever needs it
Also (as I already suggested), it exports easily to Excel, PDF, and other formats.
我们一直在使用 BIRT，它对我来说有一个陡峭的学习曲线，直到我意识到它有多少所见即所得的功能（我开始直接编辑 xml 源代码，我不推荐这样做。）有一些特定于输出的技巧（例如使用0 左边距，以便在输出为 XLS 格式时不会出现空白 A 列），但在大多数情况下，它可以快速且易于使用、编辑和预览。
在一个报告中混合不同数据集是多么容易，这也给我留下了深刻的印象。 虽然不是灵丹妙药，但它是一个比 99.999% 的人自己构建的更好的全能工具。
We've been using BIRT which had a steep learning curve for me until I realized how many WYSIWIG features it had (I started editing the xml source code direct, which I don't recommend.) There are some output specific tricks (like using a 0 left margin to not get a blank A column when outputting to XLS format) but for the most part it's quick and easy to use, edit and preview.
I have also been impressed on how easy it is to intermix different datasets in a single report. While not a silver bullet, its a better all around tool than 99.999% of people are going to build on their own.
是一个积极的建议，不如说是一个针对水晶报告的警示故事……与其他人一样，获得正确版本的水晶运行时很重要，但这样做后，我仍然遇到了这个问题：
花了两周时间在论坛上搜索并寻求建议，最终在他们的论坛上得到了水晶体的回复。 表示他遇到过类似的问题，与将 MS Paint 设置为特定文件扩展名的默认应用程序有关。
在这一点上，我们放弃了尝试（在我说服我的老板这不是一个小便的答案，而是实际上是水晶的正式回应之后）。 大约一个月后，我们轻松地迁移到新服务器（报告起作用的地方），但说实话，我不会再碰它们了……
哦，并且已经使用了 SSRS，发现它对于大多数事情都非常好（特别是最重要的事情）。最新版本）。
This isn't so much a positive suggestion, but more of a cautionary tale against crystal reports... As with other people, getting the right version of the crystal runtime is important, but having done that, I still had this problem:
Spent two weeks trawling forums and looking for advice, eventually got a response from a crystal body on their forums. Suggested that he had seen a similar problem to do with MS Paint being set up as the default application for a certain file extension.
At this point, we gave up trying (after I convinced my boss that this wasn't a take the piss answer, but actually a formal response from Crystal). Handily we were migrating to new servers about a month later (where the reports worked), but honestly, wouldn't touch them again...
Oh, and have used SSRS and found it to be pretty good for most things (particularly the most recent version).
“给他们数据，他们会因此喜欢你”
在我过去使用过的方法和工具中，我会根据能力/多功能性/可用性/部署速度按以下顺序对它们进行排名。 我将成本排除在外，因为虽然它始终是一个因素，但对每个人来说都是不同的因素。
1 是 Cognos（版本 8）
2 是 SQL Server Reporting
3 是 Crystal Reports
4 是自定义编写的代码
我没有使用任何提到的其他工具。 Cognos 8 简直太棒了。 虽然价格昂贵，但您只受您的想象力的限制。 它可以做任何事情。
"Give them data and they will love you for it"
Out of the methods and tools I've used in the past, I would rank them in the following order based on abilities/versatility/usability/speed to deploy. I'm leaving cost out of it because while it is always a factor it is a different factor for everyone.
1 is Cognos (version 8)
2 is SQL Server Reporting
3 is Crystal Reports
4 is Custom written code
I haven't used any of the other tools mentioned. Cognos 8 is nothing short of awesome. While pricey, you are only limited by your imagination. It can do anything.
1) 我认为 Reporting Services 非常适合大多数需求，在开发基于表格的报告和矩阵报告（向下钻取 - 类似功能的枢轴）时。考虑到 Cognos 等的价格。中小企业甚至无法梦想获取 Congns AFAIK
2) 可以调用报告计划/订阅功能将报告发送给一组用户（数据驱动）以交付报告。 通过编写 .Net 代码，可以将订阅传送到自定义位置，例如 SFTP。
3) 使用报表模型，最终用户可以拖放列并开发自定义报表
注意：
1) 一旦您开发了非常复杂的图形/仪表板类型的报表 - 涉及在 A4 中显示的很少的图表和小表格，它就会变得更加棘手。 报表设计器（我们用来设计报表的工具）和Web 显示使用不同的渲染引擎。 因此，如果您开发复杂的图形报告，最好经常部署报告并查看它们的外观。
2) 如果您编写自定义功能，则可能必须更改 XML 配置文件（RSReportServer.Config 等）。 如果编辑过程中出现任何问题，ReportServer 服务可能会停止。 因此，在进行任何自定义操作之前请务必小心备份
1) I would think Reporting Services is very good for most of the needs, when in comes to developing table based reports and also matrix reports (drilldown - pivot like functionality).Considering the price of Cognos etc. An SME can't even dream of getting Congns AFAIK
2) Report Scheduling / Subscription functionality can be invoked to send reports to a set of users (data driven) to deliver reports. Subscriptions can be delivered to custom locations such as an SFTP, by writing .Net code.
3) Using Report Models, end user can drag and drop columns and develop customized reports
To Note:
1) It can get trickier once you develop really complex graphical/dashboard kind reports - which involve few charts and small tables to be displayed in A4. Report Designer (the tool we use to design reports) and Web display use different rendering engines. So it is better if you deploy the reports often and see how they look, if you develop complex graphical reports
2) If you write custom functionality, you may have to change the XML configuration files(RSReportServer.Config etc). If there is any problem in the edit, ReportServer service may stop. So be careful to back up before doing anything custom
我们使用 Cognos，它是一个相当复杂的系统，但非常强大。
We use Cognos, it's a fairly complex system, but very powerful.
我有一个小型报告集，在 2 个月内制作完成：
比水晶报告至少快 10 倍；
轻松编辑；
.net公式；
使用方便；
代码使用量小；
序列化和反序列化（快速且小）；
极度安全；
多线程；
没有错误；
i have a small reporting set, made in 2 months:
at least 10 times faster than crystal reports;
easy editing;
.net formula;
easy usage;
small code usage;
serialization and deserialization(fast and small);
extreme security;
multi threaded;
no errors;
我们曾经使用过 MS Reporting Services，但我们对此完全不满意。
原因：
现在我们使用 Stimulsoft Reports。 它没有像 MS Reporting Services 这样的限制，我们和您的用户都对此感到满意。
We had used MS Reporting Services, but we was completely unhappy with it.
Reasons:
Now we a using Stimulsoft Reports. It have no such limitations like MS Reporting Services, and we and your users are happy with it.
Tableau software 是一款令人惊叹的工具，可用于运行报告并轻松进行深入分析
Tableau software is an amazing tool to run your reports and get easily deep throught analysis
对于简单的报告，我使用 Visual Studio 中包含的标准 ReportViewer。
对于更复杂的报告和需要更高性能的报告，我使用了 Report Sharp Shooter 和 devExpress XtraReports。 令人惊讶的是，在这两种产品中创建表格并不像应有的那么容易，但它们都比 ReportViewer 更快，并且可以很好地处理多列报告、条形码和聚合数据。
For simple reports I use the standard ReportViewer included in Visual Studio.
For more complicated reports and ones that require more performance I've used both Report Sharp Shooter and devExpress XtraReports. Surprisingly, in both products creating tables isn't as easy as it should but both are faster than ReportViewer and handle extremely well multi-column reports, barcodes and aggregate data.
我们使用带有 Oracle 后端的 Cognos。 我们还使用 Spotfire 在 Cognos 之上进行可视化。
Cognos with an Oracle backend is what we use. We also use spotfire for visualization on top of cognos.
我是 Windward 的首席技术官，我确实相信 Windward Reports 是迄今为止最容易使用的，而且您与任何其他报告相比，它可以做更多的事情 - 这两个特征都是出于同样的原因，您可以在 Word、Excel 和 Microsoft 中设计报告。 微软幻灯片软件。
至于生成的报告，它速度快、坚如磐石，将其合并到您的程序中只需 3 行代码。
I'm the CTO at Windward and I do believe that Windward Reports is by far both the easiest to use and you can do more with it than any other reporting - and both traits are for the same reason, you design your reports in Word, Excel, & PowerPoint.
As to the generated reports, it's fast, it's rock solid, and incorporating it into your program can be as little as 3 lines of code.
我工作的地方使用 Crystal Reports。 它有很多限制，我们发现我们自己在数据库过程和视图中执行几乎所有逻辑。
需要注意的一个限制是 Crystal Reports 不允许多层子报表。 换句话说，子报表中不能包含子报表。
We use Crystal Reports where I work. It has quite a few limitations, and we find ourselves doing almost all of the logic in Database procedures and Views.
One limitation to note is that Crystal Reports does not allow multiple layered sub-reports. In other words, you cannot have a sub-report inside a sub-report.