August 19, 2010 at 8:40 am
I've been noticing issue during setting up transaction replication on sql server 2005. Here is configuration:
Sourece server =16GB RAM Target server=16GB
All other database replication is working fine except 230GB db. During first time refresh server looks hung.
following message:
Error: 14151, Severity: 18, State: 1.
[310] 8 processor(s) and 16381 MB RAM detected
Replication Warning: Long merge over dialup connection (Threshold: mergeslowrunduration)
Replication Warning: Slow merge over dialup connection (Threshold: mergeslowrunspeed)
and it's taking longer.
Is there any way I can avoide initial refresh during setup. I'm using pull subscriber. Can I break whole database into few sets like table starting with A-H will be in one batch, I-P in another and so on?
what would be impact on source server by doing above?
Please advice any option except backup & restore.
August 19, 2010 at 9:18 am
You can run the snapshot agent to get the initial snapshot, and have it save to disk locally (make sure you don't select compression, since there is more than 2gb of data and it will fail).
Zip/rar the snapshot directory, send it to your target server using whatever method you choose (FTP, put on flash drive and physically move, etc), then on the subscriber, go to replication -> local subscriptions, and Properties of your subscription. Under 4. Snapshot, change the Snapshot Location to Alternate Folder, and then point it to the locally copied files after you unzip them (into a \unc\ dir, like it creates them on the publisher).
It should apply the snapshot locally, and then start syncing with the publisher when done. This will take a while but it won't be using the network, so it wont try to cache too much into ram before it starts to apply it.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply