September 30, 2008 at 2:24 am
Hi,
I'm using simple transactional replication - one way data-changes from the publisher to the subscriber. Can I avoid data-changes made directly on the tables of the subscriber by making the tables read-only for local data-changes, but allowing the data-changes made by the replication?
Thanks for your help!!
Torsten
September 30, 2008 at 2:33 am
You can use SQL security to create a login/role that has only read access to the tables in your subscriber, and only give the account that you are running your replication agent under write access.
September 30, 2008 at 4:41 am
Thanks for your reply.
To guarentee read-only-access to tables via security rights could be a solution. But isn't there any solution implemented with the replication itself, which would be easier to implement?
Simple transactional replication with updateable tables as default always risks integration problems. So I thought there might be another solution.
September 30, 2008 at 4:55 am
torstentiedt (9/30/2008)
Thanks for your reply.To guarentee read-only-access to tables via security rights could be a solution. But isn't there any solution implemented with the replication itself, which would be easier to implement?
There may be a way within replication, you could add triggers or something, But i doubt it will be easier than setting up security which is a fairly simple process in sql 2005 post a question on here if you need any help setting this up
Simple transactional replication with updateable tables as default always risks integration problems. So I thought there might be another solution.
It is important to check what data you are replicating, quite often there are only a few core data tables that actualy need replication, rather than replicating everything.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply