replication does not work properly

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

If the connection between the servers to be disconnected after 72 hours
replication does not work properly. Please help me

Posted 22-Jun-11 0:09am

mishgan2010

Updated 22-Jun-11 0:17am

Prerak Patel

v2

Add a Solution

Comments

Prerak Patel 22-Jun-11 6:17am

Not clear what you are asking. Elaborate more.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dylan Morley · Answer 1 · 2011-06-22T00:20:00

Are you talking about transaction retention? Have a look at this thread[^] - post by tkizer.

It also depends on how long the connection was broken. The default of the distributor is to delete the data after 72 hours, even if the transactions haven't been delivered to the subscriber. So if you are beyond the 72-hour window, then you'd have to start from a new snapshot. You can change the 72-hour retention via the distributor properties or the SQL distribution cleanup job. Please note that increasing the retention could cause performance issues, which could lead to replication latency.

Have a look at this article as well, 'Maximum Retention Time'

http://www.sqlservercentral.com/articles/Stairway+Series/72322/[^]