January 30, 2012 at 7:59 am
Hi Gurus,
I have a query for one scenario on replication. My case is:
I have monthly deployment on my DB server during this deployment which include both DDL and DML changes lock the table and my application on PROD env suffer from performance.I do agree this is due to the locking nature.
If I set up transactional replication with two server and during deployment let my application connect to second server and I do the deployment on the primary server once done I will sync the data.
Is this solution is fine ? Do I have to consider any other points?
Please share your thoughts.
"More Green More Oxygen !! Plant a tree today"
January 30, 2012 at 9:21 am
It's not quite clear what your deployment is. And how this locks things.
If you're changing schema, then there's a lock while schema is altered. Most changes can flow through replication, but you'd need to read the BOL section on replication to see if your changes would. Also, if you're adding objects, then you're adding new articles to your publication, which means more admin work.
In terms of adding data, again, it depends on how your deployment must work. Replication can do a good job of this, and I know people that have multiple databases (1/client) and use a master db to deploy changes which flow through, but the DDL changes are limited.
January 30, 2012 at 9:22 pm
Thanks Jones.
Let me do the small testing and check.
"More Green More Oxygen !! Plant a tree today"
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply