在 SQL Express 2005 和 SQL Server 2008 标准版之间备份数据
我正在开发一个应用程序，需要在 SQL Express 2005 和 SQL Server 2008 之间备份数据。我的客户端安装了 SQL Express 2005，需要定期将数据备份到在 SQL Server 2008 上运行的服务器数据库。客户端数据库还从服务器接收一些新数据并需要自行更新。问题是我该怎么做？请帮忙。
I am developing an application which needs to backup data between SQL Express 2005 and SQL Server 2008. My client runs with an installation of SQL express 2005 and needs to periodically back up data to a server database running on SQL Server 2008. The client db also receives some new data from server and needs to update itself. The question is HOW DO I DO IT ? Please help.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
有许多解决方案，具体取决于您的定期含义以及 SQL Server 2008 和 SQL Server 2005 数据库的使用情况。假设 SQL Express 2005 客户端数据库是一个控制自己数据的应用程序，但最终需要将这些更改合并到 SQL Server 2008 数据库中，那么合并复制可能是一个很好的解决方案。 SQL Server 2008 数据库将是发布者，SQL Express 2005 将是订阅者（SQL Express 只能是订阅者）。
There are many solutions depending on what you mean by periodically and the use of the SQL Server 2008 and SQL Server 2005 databases. Assuming that the SQL Express 2005 client database is an application that controls its own data but eventually needs to merge those changes into the SQL Server 2008 database, then Merge Replication probably would be a good solution. The SQL Server 2008 database would be the Publisher and the SQL Express 2005 would be the subscriber (SQL Express can only be a subscriber).
您可以查看 Service Broker 。它可以轻松地在 SQL Server 2005（甚至 Express）和 SQL Server 2008 之间交换数据，因为协议是 2005 和 2008 之间完全兼容。
设置SSB比设置复制要困难一些，不仅仅是一个向导，您必须编写代码来处理数据的传输和接收。但与基于复制的解决方案相比，它更加灵活、更容易升级、性能更高且可扩展性更强。
You can have a look at Service Broker. It can easily exchange data between SQL Server 2005 (even Express) and SQL Server 2008 as the protocol is completely compatible between 2005 and 2008.
Setting up SSB will be a bit harder than setting up Replication, is not just a wizard, you will have to write code to handle the transmission and receiving of your data. But is significantly more flexible, easier to upgrade later, higher performance and more scalable than replication based solutions.