复制情况的最佳实践
我刚刚损失了几乎一天半的时间来尝试为异地服务器进行拉复制。在经历了这次经历的痛苦之后，我现在想它不应该这么难，所以也许我做错了。我从来没有让它工作过，我不得不去推送复制。
情况是这样的。我们有一个异地托管的虚拟服务器，它将作为公共 Web 应用程序的数据库。我们希望将内部数据库中的一些表中的所有数据推送到这个场外位置，并且必须几乎立即完成，以便网络信息是最新的。我们不想设置 VPN，因为如果该计算机受到威胁，我们不希望出现该漏洞。
如果 sql server 复制不是最好的方法，你会怎么做？
仅供参考：发布者 = SQL Server 2005 &订阅者 = SQL Server 2008 Web 版
I have just lost pretty much a day and a half trying to get pull replication going for an off site server. After experiencing the pain that was this experience I am now thinking it shouldn't be this hard so maybe I am doing it wrong. I never did get it to work, I had to go to push replication.
Here is the situation. We have a virtual server being hosted off site that will a database for a public web application. We want to push all the data from a few of our tables in our internal database to this off site location and it has to be done almost instantaneously so that the web information is current. We don't want to set up VPN because if that machine gets compromised we don't want that vulnerability.
If sql server replication is not the best method how would you do it?
FYI: Publisher = SQL Server 2005 & Subscriber = SQL Server 2008 Web Edition
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
那么，如果您希望它快速且易于管理，一种解决方案是设置合并复制拓扑，将主服务器作为发布者，将托管服务器作为订阅者。然后可以通过 http 完成复制，因此无需 VPN。
请注意：网络复制并不像在浏览器中打开页面那么简单！您可以在此处找到一些有趣的信息
我没有安装SQL Studio这台机器，但我想您可以以这样的方式参数您的订阅，即仅将下载复制到订阅者，而上传将被忽略。
通过每分钟从订阅者运行复制脚本（它是一个 BAT 文件）（通过任何计划任务管理器），您可以对订阅者的表进行准即时更新。
Well, if you want it to be fast and easy to manage, one solution is to set a merge replication topology, having your main server as a publisher, and the hosted server as a suscriber. Replication can then be done through http, thus without vpn.
Be careful: web replication is not as straighforward as opening a page in your browser! You can find some interesting infos here
I do not have SQL Studio on this machine, but I guess you can parameter your subscription in such a way that only downloads will be replicated to the suscriber, while uploads will be ignored.
By running the replication script (it's a BAT file) from the suscriber every minute (through any scheduled tasks manager), you can have a quasi-instantaenous update of your suscriber's tables.