Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jjradha
Starting Member
5 Posts |
 Posted - 2012-11-12 : 09:42:53
|
| Hi all,I have a 350+ GB database that is replicated using MERGE replication to over 350 sites accross the country (UK).The MSMerge tables are constantly involved in any sort of operation and as a result of this, I have lots of WAITS suggesting a IO bottleneck, (also locking and blocking).example of waits: PAGEIOLATCH_SH,PAGEIOLATCH_EX, LCK_M_S, LCK_M_X to mention a few.example of Avg.Disk queu Length: 100, but it can be 165, and picks to 1000 sometimes on the D: drive only (DATA).I have only one filegroup (D: drive)I have 16 disks.I was considering adding a filegroup, put the file on the Backup drive (only used at night) R: drive.and put there all the INDEXES of the MSMERGE tables, or the MSMERGE tables themselves.I wonder if anyone has had this sort of problem and how it has been dealt with.regardsmarcelo |
|
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2012-11-12 : 15:11:05
|
| If your replication activity is your bottleneck, have you considered putting the distributor on a separate SQL Server?=================================================We are far more concerned about the desecration of the flag than we are about the desecration of our land. -Wendell Berry |
 |
|
|
|
|
|
MSMERGE tables on a different FILEGROUP