We have an installed site with two SQL2005 servers (workgroup, SP2).
At the publisher we recently (yesterday) bulk inserted about 2million lines
into a table from a third server that's going to be part of the replicating
group. However, since importing these records (using 'Import Data' to get
the data in and then running a no-change update to make replication aware of
them) the performance has become dreadful. The hard-drive is swamped with
disk writes.
The first symptom that something was wrong was when replication started
timing out, even when I turned off all subscriptions except for one - and
that one didn't have any of its tables modified by the import. Even putting
the agent on a slow profile with extended query timeouts doesn't help.
Any suggestions?
Many thanks.
Jim
--
"When one of the local cats, an especially fluffy creature with a vast
tail, rushed down the street towards me the other day, mewing delightedly,
I have to admit it was probably shouting 'HAZ CHEZBURGR?' " - Bella, ucsm
At the publisher we recently (yesterday) bulk inserted about 2million lines
into a table from a third server that's going to be part of the replicating
group. However, since importing these records (using 'Import Data' to get
the data in and then running a no-change update to make replication aware of
them) the performance has become dreadful. The hard-drive is swamped with
disk writes.
The first symptom that something was wrong was when replication started
timing out, even when I turned off all subscriptions except for one - and
that one didn't have any of its tables modified by the import. Even putting
the agent on a slow profile with extended query timeouts doesn't help.
Any suggestions?
Many thanks.
Jim
--
"When one of the local cats, an especially fluffy creature with a vast
tail, rushed down the street towards me the other day, mewing delightedly,
I have to admit it was probably shouting 'HAZ CHEZBURGR?' " - Bella, ucsm
Comment