locked
SQL Server Express and SQL Server Workgroup RRS feed

  • Question

  • Hi,

     

    We have a situation where we need to run an application at several remote locations. Each location will run the application independently and syc with the head-office twice a day to exchange any updates. The head-office DB will contain the data from all the locations but each location will have only its respective data. The expected number of users at the head-office is 6 while each remote location will have 1-2 users. The syncing mechanism will be managed on the application level. In order to keep the cost low we plan to run SQL Express on the remote locations and SQL Workgroup or SQL Standard at the head-office. The amount of data at the remote locations is not expected to reach 4GB anytime soon and we consider 1GB is enough for 1-2 users. Are there any other pitfalls falling such a model?

    Wednesday, July 16, 2008 4:33 AM

Answers

  • This is pretty common and only thing you should be careful while designing and developing Data Synchronization module is Conflict resolution. Ie same row is updated in many place what to do. IF you do not have that scenario the I do not think there is any problem with the model. You may also check the Merge replication option , but since its express edition you have limitation in that aspect as well.

    Madhu

    SQL Server Blog

    SQL Server 2008 Blog

     

    Wednesday, July 16, 2008 4:52 AM

All replies

  • This is pretty common and only thing you should be careful while designing and developing Data Synchronization module is Conflict resolution. Ie same row is updated in many place what to do. IF you do not have that scenario the I do not think there is any problem with the model. You may also check the Merge replication option , but since its express edition you have limitation in that aspect as well.

    Madhu

    SQL Server Blog

    SQL Server 2008 Blog

     

    Wednesday, July 16, 2008 4:52 AM
  • Thanks for a prompt reply. We dont foresee any issues with conflict resolution as different parts of the database will be updated from each location.

    Wednesday, July 16, 2008 5:24 AM
  • Out of the box, SQL Server Express can only act as a subscriber in a replication unless you implement a custome one using application codes. You can create an application that dumps the data to be synched in a file and use a column to check if the data is already replicated in both directions when you do the import/export.

    Wednesday, July 16, 2008 6:34 AM