I'm looking to implement SQL Server Reporting Services as our standard reporting platform in our company. We were trialing Crystal Reports, but alas it seems to be plagued by issues.
我希望将SQL Server Reporting Services作为我们公司的标准报告平台。我们正在试验Crystal Reports,但是它似乎受到了问题的困扰。
SQL Server Reporting Services looks to be a great product, but I have a concern or two.
SQL Server Reporting Services看起来是一个很棒的产品,但我有一两个问题。
I have some existing web apps in ColdFusion, and the backend is in MySQL. If I move forward with SQL Server Reporting Services, how should I set up my environment? Is there a JDBC connector or is ODBC the only way to talk to this?
我在ColdFusion中有一些现有的Web应用程序,后端在MySQL中。如果我继续使用SQL Server Reporting Services,我应该如何设置我的环境?是否有JDBC连接器或ODBC是与此通信的唯一方式?
How does it integrate for the user? Will I need to re-authenticate the user to view the reports? Will I need to put a link in ColdFusion to link to the Reporting Services system? Is there a way to make it seamless for the user?
它如何为用户集成?我是否需要重新验证用户以查看报告?我是否需要在ColdFusion中添加链接以链接到Reporting Services系统?有没有办法让用户无缝?
Should I port all the backend to SQL Server to fully leverage the SQL Server platform? Should I convert my existing apps to ASP.NET, and make the entire platform SQL Server / ASP.NET?
我应该将所有后端移植到SQL Server以充分利用SQL Server平台吗?我应该将现有的应用程序转换为ASP.NET,并使整个平台成为SQL Server / ASP.NET吗?
It's not too bad in the fact that the existing apps / MySQL aren't of a size that is too big to port. So I guess just looking for some best practice advise to see if its okay to use the reporting services component on its own, or if I'm much better to consolidate everything into a Microsoft solution.
现有的应用程序/ MySQL的大小不是太大而不能移植,这并不算太糟糕。所以我想只是寻找一些最佳实践建议,看看它是否可以单独使用报告服务组件,或者我是否更好地将所有内容整合到Microsoft解决方案中。
1 个解决方案
#1
I think it'll be easier than you think!
我认为这比你想象的要容易!
-
Reporting Services will happily pull reports from any OLEDB or ODBC source, and MySQL has ODBC drivers, so there's no problem getting at your data through an SSRS report.
Reporting Services将很乐意从任何OLEDB或ODBC源提取报告,并且MySQL具有ODBC驱动程序,因此通过SSRS报告获取数据没有问题。
-
You can set up the authentication in a number of ways. If your users are already authenticated in your Windows domain, this will be easier:
您可以通过多种方式设置身份验证。如果您的用户已在Windows域中进行了身份验证,则会更容易:
- SSRS needs to know who is viewing the report. It will allow anonymous viewing (if you enable it; it's off by default), but if you're using IE and are logged in to the same domain as the IIS server, it's completely transparent
- SSRS can then use this identity to connect to the data source, or it can use another identity. This is configurable per report or per data source.
SSRS需要知道谁在查看报告。它将允许匿名查看(如果您启用它;默认情况下它是关闭的),但如果您使用的是IE并登录到与IIS服务器相同的域,则它是完全透明的
然后,SSRS可以使用此标识连接到数据源,也可以使用其他标识。这可根据报告或每个数据源进行配置。
-
One thing you could do is embed your reports within iframes in your coldfusion pages. This would make the whole thing seamless. The reports are accessible by sending an appropriately formed URL to the server, so it's quite flexible.
您可以做的一件事是将您的报告嵌入到您的coldfusion页面中的iframe中。这将使整个事情变得无缝。可以通过向服务器发送适当形成的URL来访问报告,因此它非常灵活。
As for changing everything to ASP.NET, you'll really only get benefits from that if you ever need to write (and integrate with) your own code to manage the reporting server, or write custom extensions (data providers, delivery extensions and the like), but in my experience this is so rare as to be not worth considering. Go with what you have for now.
至于将所有内容更改为ASP.NET,如果您需要编写(并集成)自己的代码来管理报表服务器,或者编写自定义扩展(数据提供程序,交付扩展和但是根据我的经验,这是非常罕见的,不值得考虑。继续你现在所拥有的。
#1
I think it'll be easier than you think!
我认为这比你想象的要容易!
-
Reporting Services will happily pull reports from any OLEDB or ODBC source, and MySQL has ODBC drivers, so there's no problem getting at your data through an SSRS report.
Reporting Services将很乐意从任何OLEDB或ODBC源提取报告,并且MySQL具有ODBC驱动程序,因此通过SSRS报告获取数据没有问题。
-
You can set up the authentication in a number of ways. If your users are already authenticated in your Windows domain, this will be easier:
您可以通过多种方式设置身份验证。如果您的用户已在Windows域中进行了身份验证,则会更容易:
- SSRS needs to know who is viewing the report. It will allow anonymous viewing (if you enable it; it's off by default), but if you're using IE and are logged in to the same domain as the IIS server, it's completely transparent
- SSRS can then use this identity to connect to the data source, or it can use another identity. This is configurable per report or per data source.
SSRS需要知道谁在查看报告。它将允许匿名查看(如果您启用它;默认情况下它是关闭的),但如果您使用的是IE并登录到与IIS服务器相同的域,则它是完全透明的
然后,SSRS可以使用此标识连接到数据源,也可以使用其他标识。这可根据报告或每个数据源进行配置。
-
One thing you could do is embed your reports within iframes in your coldfusion pages. This would make the whole thing seamless. The reports are accessible by sending an appropriately formed URL to the server, so it's quite flexible.
您可以做的一件事是将您的报告嵌入到您的coldfusion页面中的iframe中。这将使整个事情变得无缝。可以通过向服务器发送适当形成的URL来访问报告,因此它非常灵活。
As for changing everything to ASP.NET, you'll really only get benefits from that if you ever need to write (and integrate with) your own code to manage the reporting server, or write custom extensions (data providers, delivery extensions and the like), but in my experience this is so rare as to be not worth considering. Go with what you have for now.
至于将所有内容更改为ASP.NET,如果您需要编写(并集成)自己的代码来管理报表服务器,或者编写自定义扩展(数据提供程序,交付扩展和但是根据我的经验,这是非常罕见的,不值得考虑。继续你现在所拥有的。