October 17, 2011 at 2:43 pm
We are planning to set up one way transactional replication for several databases and would like to schedule the replication to run every 15 minutes. Most often the data being replicated will easily fit into that 15 minute window. Occasionaly large updates to one or two of the tables might occur that could potentially take longer than 15 minutes to be applied at the subscriber ( we sometimes experience network lantecy ). Will this cause a problem ? Will replication continue at the next 15 minute interval even if the last replication has not completed at the subscriber?
I am very new to replication and your advice is appreciated.
thanks
October 17, 2011 at 3:35 pm
Transactional Replication should run all the time...as it is by default, but if you do schedule it somehow there shouldn't be an issue with it running into one another. The job(s) won't start if it is already running and if an overlap occurs, it will just pick up at the "next" scheduled start time.
Also, look at the columns you're replicating, omit anything/everything (i.e xml, blob, text) you won't be using on the other end...especially if you already have issues with network I/O.
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 17, 2011 at 4:22 pm
We keep several servers sync'd hourly using this method. You can set up whatever shedule you like and you can change those schedules on the job if you like as well.
October 17, 2011 at 6:25 pm
Thanks for the feedback. We only have nvarchar,int and date fields not very heavy in transactions most of the time so don't expect too many issues but do have periodic (three times a week) larger data flows into a few tables.
Appreciate you sharing your experience.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply