August 9, 2012 at 2:06 am
Hi all
We have an application that (Dynamics AX) which we perform regular releases to. The database we release to is part of a transactional replication process. We don't actually control the releases as they are done through the AX client which causes a problem.
On some occasions the releases perform a sp_rename which breaks replication and at present we end up scripting off the entire replication, dropping it, performing the release, re-creating the replication and re-initialising a new snapshot.
This can take some time (4hrs in some cases) and I have been unsuccessfully trying to think of a way to avoid this and speed up the process.
Is anyone able to think of a way round this?
Thanks
August 9, 2012 at 2:28 am
If you have no control over the release process, at least you could apply the changes to a test environment before going live. If it breaks the replication in test, it can't be applied in production.
Replication is very tricky and applying scripts to a published database must be tested thoroughly.
-- Gianluca Sartori
August 9, 2012 at 2:32 am
We do apply it to test at first and know that it is going to break replication. The ERP releases are more important than the work required to fix the replication unfortunately.
August 9, 2012 at 2:50 am
Kwisatz78 (8/9/2012)
We do apply it to test at first and know that it is going to break replication. The ERP releases are more important than the work required to fix the replication unfortunately.
Then, I guess there's not much you can do.
However, if you could use a backup instead of a snapshot to initialize the subscriber, I think you could cut down the time.
-- Gianluca Sartori
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply