October 10, 2006 at 8:33 am
I wonder if a subscriber database can be made read-only? WOuld that conflict with the replicationprocess?
Greetz,
Hans Brouwer
October 11, 2006 at 5:19 am
Use snapshot replication. If they enter data, it will be replaced with the next snapshot.
or/and
change the permissions on the subscriber database to "datareader" only
October 11, 2006 at 5:51 am
Snapshot would pose problems. Users wish the targetdb to be up te date realtime...
Greetz,
Hans Brouwer
October 12, 2006 at 10:43 pm
Why don't you give the users of that database db_datareader role and not db_datawriter role, that way the user can only access the information and not change it. As long as the login that controls replication is not a member of that group replication should still work ok.
October 13, 2006 at 5:00 am
Why don't you give the users of that database db_datareader role...
That we be the best way to do this. However, the company I'm working currently has NO info written down on who and what is connecting to this database. Me and my collegua are working on this, we have most of the users/apps inventorized(and those are many!), we have not yet determined what these users/apps need for authentication... Until that time a read-only would seem prudent.
Greetz,
Hans Brouwer
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply