February 16, 2011 at 12:21 pm
I'm helping to identify requirements for a DR plan via replication, but since most of our DBs are in simple recovery mode due to a number of reasons, it is difficult for me to tell how much data is changing per day.
Clearly, I know the size of the DB for the initial replication, but I'm trying to figure out how much it changes or how much data would need to be transferred to an offsite location to keep the offsite DB relatively current. Is anyone aware of a way to tell how much data is moved due in an existing replication for some time period?
I know that I could use something like sp_whoisactive to tell me about resources I've used since a system started on the receiver of a replication job, but am stuck getting any further. Any suggestions?
Thanks in advance!
February 16, 2011 at 12:40 pm
Why not change the recovery mode to full and start doing hourly translog backups for a week. That should give you an idea of data volume and peak activity times/days.
The probability of survival is inversely proportional to the angle of arrival.
February 16, 2011 at 12:50 pm
Being that information is stored as commands and transactions at the distribution database I don't know that you will find the answer there. It definitely seems like your best option is to go with the log backups for a period of time.
The only other thing that I could think of is to create a second subscriber database with the appropriate article structures in there but have it empty. Then create a new subscription to that database as well as what you have already and check the size after some period of time. That should get you the information.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply