I need to set up this scenario:
我需要设置这个场景:
A SQL Server 2005 database will create a transactional replication subscription from another database to populate a set of lookup tables. These lookup tables will then be published as a merge replication publication to the client's SQL Server Mobile.
SQL Server 2005数据库将从另一个数据库创建事务复制订阅以填充一组查找表。然后,这些查找表将作为合并复制发布发布到客户端的SQL Server Mobile。
I remember seeing a similar scenario defined in the SQL Server Books Online somewhere, but I was unable to find the link anymore. I hope someone can help me find it, or otherwise point me to any other similar links.
我记得在某个地方看到了SQL Server Books Online中定义的类似场景,但我无法再找到该链接。我希望有人可以帮我找到它,或者指出任何其他类似的链接。
3 个解决方案
#1
2
Okay, I managed to get the answers I needed at the MSDN SQL Server Replication forum.
The article I was looking for is called: Republishing Data.
好的,我设法在MSDN SQL Server复制论坛上获得了我需要的答案。我正在寻找的文章称为:重新发布数据。
Apparently, it is located within "Advanced Replication Features and Internals" of the "Configuring and Maintaining Replications" section. It's a little non-obvious, so I spent most of my time looking in the "Replicating Data Between a Server and Clients" section, instead of there. Good to know, as there seems to be a number of other special scenarios worth looking at in there.
显然,它位于“配置和维护复制”部分的“高级复制功能和内部”中。这有点不明显,所以我花了大部分时间来查看“在服务器和客户端之间复制数据”部分,而不是那里。很高兴知道,因为在那里似乎还有许多值得关注的特殊场景。
#2
0
I do not get the interest of having a transactional replication to generate lookup tables. Such tables are not made to be updated from the client side, so why do you want to combine transactional + merge replication when you don't have the data modified by the subscribers?
我没有兴趣使用事务复制来生成查找表。这些表不是从客户端更新的,那么当您没有订阅者修改数据时,为什么要组合事务+合并复制?
#3
0
Maybe the original scenario is not clear, so let me clarify.
也许最初的情况并不清楚,所以让我澄清一下。
The database where the original lookup tables are located either remotely with bad network connection, or operated under heavy load. This approach was suggested so that the lookup tables are replicated to another database which all merge replication with the clients will be performed.
原始查找表位于远程网络连接不良或在高负载下运行的数据库。建议使用此方法,以便将查找表复制到另一个数据库,该数据库将执行与客户端的所有合并复制。
Of course, it may not be the most appropriate approach to our problem, so if anyone has a better idea, we'll like to hear them.
当然,它可能不是解决我们问题的最合适的方法,所以如果有人有更好的想法,我们会希望听到它们。
Still, the main reason for this question is to find an article I previously found (but stupidly did not bookmarked) which described our scenario quite well. Any possible leads to this article (title, author, similar topics, etc) are definitely appreciated.
尽管如此,这个问题的主要原因是找到我之前发现的一篇文章(但愚蠢地没有加入书签),这篇文章很好地描述了我们的场景。任何可能的导致这篇文章(标题,作者,类似主题等)肯定是赞赏。
#1
2
Okay, I managed to get the answers I needed at the MSDN SQL Server Replication forum.
The article I was looking for is called: Republishing Data.
好的,我设法在MSDN SQL Server复制论坛上获得了我需要的答案。我正在寻找的文章称为:重新发布数据。
Apparently, it is located within "Advanced Replication Features and Internals" of the "Configuring and Maintaining Replications" section. It's a little non-obvious, so I spent most of my time looking in the "Replicating Data Between a Server and Clients" section, instead of there. Good to know, as there seems to be a number of other special scenarios worth looking at in there.
显然,它位于“配置和维护复制”部分的“高级复制功能和内部”中。这有点不明显,所以我花了大部分时间来查看“在服务器和客户端之间复制数据”部分,而不是那里。很高兴知道,因为在那里似乎还有许多值得关注的特殊场景。
#2
0
I do not get the interest of having a transactional replication to generate lookup tables. Such tables are not made to be updated from the client side, so why do you want to combine transactional + merge replication when you don't have the data modified by the subscribers?
我没有兴趣使用事务复制来生成查找表。这些表不是从客户端更新的,那么当您没有订阅者修改数据时,为什么要组合事务+合并复制?
#3
0
Maybe the original scenario is not clear, so let me clarify.
也许最初的情况并不清楚,所以让我澄清一下。
The database where the original lookup tables are located either remotely with bad network connection, or operated under heavy load. This approach was suggested so that the lookup tables are replicated to another database which all merge replication with the clients will be performed.
原始查找表位于远程网络连接不良或在高负载下运行的数据库。建议使用此方法,以便将查找表复制到另一个数据库,该数据库将执行与客户端的所有合并复制。
Of course, it may not be the most appropriate approach to our problem, so if anyone has a better idea, we'll like to hear them.
当然,它可能不是解决我们问题的最合适的方法,所以如果有人有更好的想法,我们会希望听到它们。
Still, the main reason for this question is to find an article I previously found (but stupidly did not bookmarked) which described our scenario quite well. Any possible leads to this article (title, author, similar topics, etc) are definitely appreciated.
尽管如此,这个问题的主要原因是找到我之前发现的一篇文章(但愚蠢地没有加入书签),这篇文章很好地描述了我们的场景。任何可能的导致这篇文章(标题,作者,类似主题等)肯定是赞赏。