Hi,

when I synchronize my dev instance and my prod instance the process can be
long, but during this time the CPU is not used at 100% and the disks don't
do something specially.

so what's really appends?
and how can I improve this process?
what are the main component to focus on?

(my dev & prod instances are on the same box, so there is no network
transfert)

thanks.

Jerome.

Hi,

Have you run profiler on your disk IO performance to prove this?

You can also run SQL profiler to see how long each step of the synch takes,
it may me worth looking into that too.

Let me know the size, duration and hardware and we can compare notes. I
think ours takes about an hour but we do it across the network from one
machine to the other.

Also, the synch only does what it see's has actually changed, so if you full
process the source database, it'll copy it all.
--
Kyle Henly
DBA
U.K.


"Jeje" wrote:

Hi,

there is near no disk activity.
there is no IO bottleneck, the queue length is low.

the copying process is good, but the preparing process is long.
Specially if the cache is not empty.

If I execute the synchronization 2 times the second times perform better,
but if a user start accessing the target instance, then this slow down the
sync. process.
(there is no activity on the target instance, the cache contains data due to
a previous user access)

The time required to sync. can take up to 5minutes! (minimum 2min)
Database size: 700MB
Hardware:
1 * Dual Core opteron
4 Gb Ram
4 * SATA disks in Raid 0
Software:
Win 2k3 x64 + SQL 2005 x64 Ent.

its good to know that the sync tool transfert only changing informations
between the instances.
I presume that the biggest sync time is after a full process.


"Kyle Henly" <KyleHenly (AT) discussions (DOT) microsoft.com> wrote