May 10, 2005 at 9:06 am
we had a transactional replication for ca 7 GB of Data and after reinitialize all Subscriptions the distribution agent work about 16 hours to apply the snapshot and we abort them.
we set a filter on the publication so there are only 1 gb of Data and the Distribution agent needs 15 Minutes.
the profile for the Distribution agent is adapted, so the bcp batch size is reduced to 10000, the log in time out is set to 30 and the query time out on 6000 so it is not an time out.
so anyone knows this problem?
May 10, 2005 at 9:36 am
What you may want to do is bcp/dts all the data out of the tables/articles on the publisher and when setting up the replication click the option that the subscriber has the table schema and data already. Burn the data to dvd's or other media and then import into the subscriber and then start the distribution agent.
Things to watch out for:
This approach has latency, that is, if any transactions are created before you import the data into the the subscriber the replication will fail if any of the data does not match (a delete happens on puplisher before you start the distribution agent)
The only way I have found to get around this is to this out of business hours when no transactions are being created.
May 10, 2005 at 10:07 am
thx for the answer,
but thats not the way we want to go, because the same replication works by other customers.
I thought while the snapshot agent runs the tables are locked and after that the Log Reader Agent log all transactions and apply these transactions after the snapshot was apply?
the problem must exist on the target DB and i dont know what it is.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply