September 15, 2014 at 2:43 am
Hello community!
Following scenario
On the server runs an enterprise edition with the needed database.
I have a client in the field which should have a local copy of the database in case of a network failure. The database is needed on the client, as without the database the production would come to a halt. Due to their IT policy, they can only use an "Express" edition on the client.
Under normal conditions, the server database is used to select, update and insert the recipe data (master data). If a network failure occurs, the connection from the frontend is redirected to the local database where the update/select and insert should then occur.
Is it possible to replicate a table to the local database where update/insert statements can occur in case of a network failure?
The server database should not be updated by those statements.
Can I use the replication wizard for this task or should I program an SP for the replication of the tables where the local changes can occur?
Does a local update statement on a subscriber table break the replication?
The complete database will not exceed 30 MB.
Thank you for your help.
Regards,
Alex
September 15, 2014 at 2:45 am
That's just normal transactional replication. Providing the person working on the subscriber doesn't delete, insert or change the key values, updates won't break replication. Be aware that his changes will be wiped out if someone updates the same row on the publisher.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 15, 2014 at 2:51 am
Hello GilaMonster!
Thank you for the fast answer.
The key values are not updated. Local inserts will not be allowed. It is no problem if the local changes are overwritten by the server. That is exactly what the customer wants.
If the server is back again, can I force the replication agent to start a complete replication so that the local changes are overwritten by the server?
Thanks in advance.
Best regards,
Alex
September 15, 2014 at 2:53 am
Alex-489474 (9/15/2014)
If the server is back again, can I force the replication agent to start a complete replication so that the local changes are overwritten by the server?
You can invalidate the subscription and re-start the snapshot agent.
I would recommend that you mock this all up in a test lab and play with it until you're comfortable. Replication isn't hard, but it does have a few gotchas.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 15, 2014 at 2:56 am
Hello GilaMonster!
Thank you very much for your help.
I have already considered to build a test lab.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply