|
Scenario: I have 3 Servers running in different geographical locations. DataBase Log is Full and using P2P Replication to Replicate the DataBases. Everything is fine until log file grows to the limit of the disk size. What can I do here to make the log file smaller (like truncate / shrink / backup) and if I do that what happened to other 2 Servers? Are they gone down due to log file asymmetry, cause when I do that Main server's transaction log freed a little bit? Or simply... How can I make log files smaller (due to disk space problem) (in both 3 servers) without breaking the p2p replication and data corruption? Thanks for your answers...
(comments are locked)
|
|
Typically the changes made to the log on the primary server will replicate to the other servers without breaking replication (including log shipping).
(comments are locked)
|
