We have SQL Server database setup. We are setting up a replication scenarios where we have one publisher and on subscriber. The subscriber will be used as a reporting platform so that we can run all the BI queries that we need and have to hit the server that is reciving all the data from our clients. The subscriber is set to pull data in from the distributer.
我们有SQL Server数据库设置。我们正在建立一个复制方案,我们有一个发布者和订阅者。订阅者将用作报告平台,以便我们可以运行所需的所有BI查询,并且必须访问从客户端获取所有数据的服务器。订户设置为从分发者中提取数据。
We don't have many indexes on the publisher db, but we will need them on the reporting server (i.e subscriber).
我们在发布者数据库上没有很多索引,但我们需要在报告服务器上(即订阅者)使用它们。
My Question is: Will SQL Server a) allow this scenario, noting that no changes on the subscriber are pushed back the the publisher. b) if a snapshot is run I am presuming it will overwrite our indexes, can I stop this from happening? c) is this a wise course of action.
我的问题是:SQL Server a)是否允许这种情况,并指出订阅者的任何更改都不会被推回发布者。 b)如果运行快照我假设它会覆盖我们的索引,我可以阻止这种情况发生吗? c)这是一个明智的行动方案。
Thanks.
Paul Kinlan,
http://www.topicala.com/ http://www.thecompanything.com/
1 个解决方案
#1
7
The scenario you explain is a common one and one of the benefits of using replication. No changes or indexes you create on the subscriber will go to the publisher as it is a one way process. If you have to re-run the snapshot agent for some reason and re-initialize the subscriber than you will need to re-create your indexes on the subscriber. There are alot of things you can do to minimize the need to re-initialize the subscriber but some of them require some manual steps. Generally if you keep all of your index creation scripts for the subscriber up to date it usually isn't a big deal to re-run them if needed.
您解释的场景是常见的,也是使用复制的好处之一。您在订阅者上创建的任何更改或索引都不会发送给发布者,因为它是单向进程。如果由于某种原因必须重新运行快照代理并重新初始化订户,则需要在订阅服务器上重新创建索引。您可以做很多事情来最小化重新初始化订户的需要,但其中一些需要一些手动步骤。通常,如果您保持订阅者的所有索引创建脚本都是最新的,那么在需要时重新运行它们通常不是什么大问题。
#1
7
The scenario you explain is a common one and one of the benefits of using replication. No changes or indexes you create on the subscriber will go to the publisher as it is a one way process. If you have to re-run the snapshot agent for some reason and re-initialize the subscriber than you will need to re-create your indexes on the subscriber. There are alot of things you can do to minimize the need to re-initialize the subscriber but some of them require some manual steps. Generally if you keep all of your index creation scripts for the subscriber up to date it usually isn't a big deal to re-run them if needed.
您解释的场景是常见的,也是使用复制的好处之一。您在订阅者上创建的任何更改或索引都不会发送给发布者,因为它是单向进程。如果由于某种原因必须重新运行快照代理并重新初始化订户,则需要在订阅服务器上重新创建索引。您可以做很多事情来最小化重新初始化订户的需要,但其中一些需要一些手动步骤。通常,如果您保持订阅者的所有索引创建脚本都是最新的,那么在需要时重新运行它们通常不是什么大问题。