December 17, 2009 at 12:27 pm
Hello
When i set up replication (say) every 5 minutes, all the tables which are part of the
replication get written to the disk every 5 minutes and it kills the response (CPU/disk io). I am loading about 17gb/day (Approx 800Mb/hr) and it gets written every few mins..
Any way this can be reduced? Can SQL Server be made to be smart to remember what it wrote?
TIA
December 17, 2009 at 12:32 pm
What kind of replication?
What do you mean by 'written to disk'? SQL writes changes to memory initially. They're written to disk in a checkpoint operation on a regular basis.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 17, 2009 at 12:54 pm
Few more questions other than what Gail has asked.
What do you mean by replication for every 5 Minutes?
If it's Snapshot Replication running atevery 5 mins interval it would be an ideal type of replication. If you need data to be moved near real time, Transactional Replication is the way to go.
Any way this can be reduced?
Looking at the amount of data you are moving, are you sure you need to move the complete set of the data, since replication can filter the data that is not required at the subscriber, so you can make it a little bit ligher by choosing only required columns and placing filtering.
Can SQL Server be made to be smart to remember what it wrote?
What do you mean by it?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply