SQL 2008 P2P Replication Log Backing Up or Shrinking (If no space left on drive)

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...

more ▼

asked May 26, 2010 at 09:39 AM in Default

HMK gravatar image

1 1 1 1

(comments are locked)
10|1200 characters needed characters left

1 answer: sort oldest

Typically the changes made to the log on the primary server will replicate to the other servers without breaking replication (including log shipping).

more ▼

answered May 26, 2010 at 12:59 PM

CirqueDeSQLeil gravatar image

4.8k 10 11 15

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: May 26, 2010 at 09:39 AM

Seen: 1332 times

Last Updated: May 26, 2010 at 09:39 AM