SQL Server 2000, SP4 (all servers)
Transactional replication, 1 push and 1 pull (db_x and db_y on same subscriber)
No clustering involved
Tired of having to apply windows security patches and do the reboots in a controlled way for my publisher, distributor and subscriber, I am finally asking the question - do i need to do this?!
My fear is that an automatic reboot done by our WSUS server will break replication, e.g. if there are transactions being replicated while one or all of the servers goes down.
If the publisher or distributor are rebooted while there are transactions being read from the publisher's log or being written to the distribution database, then the transactions are presumably not marked as complete in the publisher. Therefore upon startup the transactions would get read from the log again and propagated to the dist db again. Would you agree?
If the distributor or subscriber are rebooted while there are transactions being applied to the subscriber, then the transactions are presumably not marked as complete in the distributor. Therefore upon startup the transactions would just get applied again, would they not?
Do you think my assumptions are valid and that i might just let WSUS do the reboots? I could always do a checksum validate the next day to be sure. (At the time of the WSUS reboot, database usage would be light, but i need to cover all angles!).
What do the rest of you do about this sort of thing?