如何将实时 SQL Server 2005 服务器与开发盒同步？
我们的网络内部有一个开发盒，外部有一个网络服务器群。
保持开发数据库与实时服务器的[不断变化的]数据库同步并保持其安全的最佳方法是什么？
是否有第三方工具可以促进这一点？
SQL Server 的内置同步功能是否足够好，或者它们是否需要将我的网络开放到不可接受的水平？
我们如何才能将其简化为“一键式”操作？
We have a development box which is inside our network and a web server farm outside.
What's the best way to keep the development database synchronized with the Live Server's [changing] Database and yet still keep it secure?
Are there 3rd party tools that would facilitate this?
Are SQL Server's built-in synchronization features good enough or do they require opening up my network to an unacceptable level?
How can we get this down to a "one-button" operation?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
是的，当然有很多成熟的第三方工具可以做到这一点（SQL Server 本身并没有真正提供太多） - 最好的是：
Red-Gate SQL Compare（针对您的结构）和 SQL 数据比较（针对数据）
ApexSQL 的 SQL Diff（针对您的结构）和 SQL Data Diff（针对数据）
Yes, of course there are plenty of well established third-party tools to do this (SQL Server itself doesn't offer very much really) - the best are:
Red-Gate SQL Compare (for your structures) and SQL Data Compare (for data)
ApexSQL's SQL Diff (for your structures) and SQL Data Diff (for data)
使用比较工具比较实时/开发数据库对于任何超过几十 MB 的数据都是一种痛苦。
当比较以“z”开头的表时，您的外键会与以“a”开头的表混淆。
我见过/使用过的选项：
我的首选选项是第 3 个：您有昨晚的定期每日快照（例如） 。最重要的是，您还可以验证您的备份并拥有参考副本。镜像/日志传送只是复制损坏。
Comparing live/dev databases with a compare tool is a pain for anything more than a few tens of MBs
By the time it's compared tables starting "z" your foreign keys are buggered up with tables starting "a".
Options I've seen/used:
My preferred option is number 3: you have a regular daily snapshot of what you had last night (for example). On top of that, you verify your backups too and have a reference copy. Mirroring/log shipping simply replicates corruption.