远程位置的 SQL Server 分析和报告服务
我们有 3 个独立的环境：生产环境、临时环境和存档/备份环境
A) 是否可以仅在存档环境上设置分析和报告服务？存档环境基本上是生产环境的副本，或者它们在原始事务发生的环境上运行是否至关重要？ （也许服务需要所有精确的日志等？）
这样做的目的是能够“减轻”生产的关键系统，并将负担转移到存档，服务可以自由地消耗更多资源，而无需查询/干扰生产环境。
B) 是否有可靠的方法来保持归档/备份的自动化和可靠性？我们正在研究 Redgate SQL 工具，但任何 (最好是开源的）这部分的建议或经验将是非常宝贵的。
We have 3 separate environments: a production ,a staging and an archive/backup environment
A) Is it possible to have Analytics and Reporting services set up only on the archive environment? The archive environment would basically be a duplicate of the production, or is it critical that they operate on the environment that the original transaction happens? (Maybe the services need all exact logs etc?)
The point of this is to be able to "lighten" the critical system that is production, and move the burden to the archive where the services can consume more resources freely, without querying/disturbing the production environment.
B) Is there a reliable way to keep the archive/backup automated and reliable? We are looking into the Redgate SQL tools, but any (preferably open source) suggestions or experience in this part would be invaluable.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
答）是的，这是一种非常常见的报告或数据仓库配置。您可以在生产副本上运行查询或构建数据仓库，以避免影响性能。
B) SQL Server 本身支持很多选项：备份/恢复、复制、日志传送。但您需要研究每一种方法的优缺点，以找到最适合的方法，例如，您需要报告系统上的数据是最新的吗？
基本上，您似乎在询问如何使用生产数据库的副本来实施报告解决方案。正如我所提到的，这是一种非常常见的情况，您可以通过谷歌搜索在此网站和其他地方找到大量信息。
A) Yes, and this is a very common reporting or data warehousing configuration. You run your queries or build your data warehouse on a copy of production, in order to avoid impacting performance.
B) There are plenty of options supported by SQL Server itself: backup/restore, replication, log shipping. But you will need to look into the pros and cons of each one to find the best fit, e.g. how up to date do you need data to be on the reporting system?
Basically, you seem to be asking about implementing a reporting solution using a copy of a production database. As I mentioned, this is a very common scenario and you will find a lot of information on this site and elsewhere by Googling.