all groups > sql server replication > september 2006 >
You're in the

sql server replication

group:

Problems Replicating Large SQL 2000 Table


Re: Problems Replicating Large SQL 2000 Table Hilary Cotter
9/7/2006 9:50:44 AM
sql server replication:
I would advise you to use a concurrent snapshot. While you can use DTS, or
bcp it is hard to get establish a water mark where your snapshot does not
contain any of the changes that occurred in your database since you started
to build your own snapshot.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



[quoted text, click to view]

Re: Problems Replicating Large SQL 2000 Table Paul Ibison
9/7/2006 2:49:30 PM
Elrond,
this is othen an issue. You could create the snapshot, zip it up, transfer
it then unzip and use the 'Alternative snapshot location' to initialize.
For the snapshot generation, you could use concurrent access option to
ensure minimum locks are taken.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Problems Replicating Large SQL 2000 Table Elrond Bishop
9/7/2006 3:39:27 PM
Hi All
I am trying to set up transactional replication on a large table (53m
records) and am batteling to get the initial snapshot to go through due to
either timeouts or locks being caused on the publication database.
Is there any way to send the initial snapshot in smaller chuncks or to DTS
the initial snapshot across and then set up the replication ?
I am able to DTS the data across without any problem but have no clue how to
synchronise the transactional replication between the 2 tables.
This is between 2 SQL 2000 databases.
Thanks in advance for your replies.




AddThis Social Bookmark Button