报告服务和 SQL Server 镜像
在具有 2 个 SQL Server 2008 SP2 Standard 服务器的安装中，我们使用镜像来为数据库提供故障转移伙伴。
数据库的用途之一是通过 SQL Server Reporting Services 提供报告。
我的问题是如何设置它以实现报告的故障转移并将成本保持在最低限度。
我可以看到一种解决方案，其中报告数据库及其使用的用户数据库都被镜像。但报告服务会进行故障转移吗？
另一种方法可能是在每个数据库服务器上安装 2 个独立的报告服务实例，其中报告数据库未镜像且两个实例都在运行。但是，如何将用户浏览器从一个入口地址重定向到正在运行的报告服务呢？
还有一个运行 SQL Server 2008 Express 的见证服务器。这可以升级到标准并运行报告服务（应该能够通过本机客户端连接进行故障转移），但报告服务本身没有故障转移。
我不知道我是否在这里遗漏了一些东西，但是如果不使用 SQL Server Enterprise 和故障转移群集解决方案，是否不可能以良好的方式做到这一点？
任何想法、想法和链接将不胜感激，但请注意，我已经阅读了互联网上的大量指南和最佳实践，但没有找到任何可以回答此问题的内容，因此请仅发布相关链接。
我从您的帖子、链接以及我的研究和测试中收集的任何信息当然都会返回到 Stackoverflow 供其他人将来参考，因为我无法想象我是唯一一个想要这样的解决方案的人。
- 斯敏特
In an installation with 2 SQL Server 2008 SP2 Standard servers we use mirror to have failover partner for the databases.
One of the purposes of the databases are to supply reports through SQL Server Reporting Services.
My question is how I set this up to have failover of the reports AND keep cost at a minimum.
I can see one solution where the reporting databases are mirrored as well as the user databases they use. But will the reporting services failover?
Another way could be to install 2 separate instances of reporting services on each database server where the reporting databases are not mirrored and both are running. But then how do I redirect the users browsers from one entry address to a running reporting service?
There's also a witness server running SQL Server 2008 Express. This could be upgraded to standard and run the reporting services (should be able to failover through native client connection), but then the reporting service it self has no failover.
I don't know if I'm missing something here but is it impossible to do this in a good way without using SQL Server Enterprise and a failover cluster solution?
Any ideas, thoughts and links would be appreciated, but be aware that I have read a lot of guides and best practices around the internet and haven't found any that answers this question so please only post relevant links.
Any info I gather from you post, links and my research and testing will of course go back to Stackoverflow for future reference for others as I can't imagine I'm the only one who would like such a solution.
- Smint
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您将需要镜像所有数据，然后在数据移动到镜像服务器时手动重新指向报表服务器。
通过镜像移动相互关联的数据库会使事情变得复杂。如果一个数据库由于某种原因离线并且镜像失败，那么所有其他数据库也会失败吗？
您可能希望有人做出这些决定，并在镜像上使用手动故障转移。
You will need to mirror all data and then manually repoint the report server when the data moves to the mirrored servers.
Moving interrelated databases with mirroring complicates things. If one goes offline for some reason and failes to the mirror, will all other databases fail as well?
You may want to have a human make these decisions and use a manual failover on the mirroring as well.