I'm running a merge replication wir multiple re-publishers and row filters on the articles. When I initialize a new latop it takes replmerg.exe about 8 minutes (!!) to check whether there might exist a partitioned snapshot - which I usually don't use.
The CPU on both the subscriber and re-publisher is 0% - what is SQL Server doing in this time......can this be reduced anyhow ?
View Complete Post