how do i prevent subscriber databases from being updated
-
good morning everybody!
my question is how do i prevent subscriber databases from being updated?
we are running sql2000, transactional replication. I understand that 'update' permission can be revoked
on the subscriber side, but the problem is if for example primary database system failed....G-d forbid
falling over will take extra time because all permission have to be re-granted. We have 'very' production
environment and every second of down time cost us.
let me re phrase my question, what is the BEST way to prevent subscriber databases from being updated?
thank you.
-
How do you handle when the primary comes back on-line? Are changes merged back in?
You can always issue an ALTER DATABASE statement putting the database into RESTRICTED_USER mode. In this case only db_owners, dbcreators, and sysadmins can come in. I am assuming whatever account performing the synchronization has this level of permissions. And if you have to do a switch over you can execute another ALTER DATABASE statement putting it into MULTI_USER mode.
K. Brian Kelley
@kbriankelley -
thank you very much, that was very helpful..
BTW is that something new, that came in with sp3a or sp4 ?
-
No, I believe it's been around since at least the SQL Server 7.0 days.
K. Brian Kelley
@kbriankelley
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply