Is there a standard practice for synchronizing SQL Server tables?
I've written an application that retrieves pricing and part options from a SQL database to generate a 3D Model of the product and create a sales proposal. My client likes it so much they want to be able to use it on laptops in the field now. The catch is, they won't have an internet connection.
I'm considering setting up a SQLite database as part of the standard installation. The SQLite database on each laptop will synchronize with the main database when the internet connection is re-established.
Are there best practices regarding synchronizing SQL tables like this? Are there any pitfalls I should consider? I'm open to all options.
Thank you.
See Introduction to Sync Framework Database Synchronization
Look at the sample Getting Started: Client and Server Synchronization which provides a simple example of offline synchronization between a central SQL Server database and SQL Server Compact Edition on the client(s). You'd probably end up using SQL Server CE for this instead of SQLite, but they are comparable.
I'm not sure how complex your application is, or how many laptops it will be installed on, but it sounds like in addition to replication of the data you may want to look at your application deployment strategy too.
Have you looked into doing a ClickOnce deployment for this application? Its a nice complement to the Sync Framework and will let you "Sync" your application updates along with data.
链接地址: http://www.djcxy.com/p/45304.html上一篇: 2个对象与Java反射之间的差异：如何？