We are currently running SQL Server 2014 with a 3-node AlwaysOn cluster. The main transactional database is going through an overall and
all systems connecting to it, is being re-designed. Once the new DB and systems are ready, it will go live at 1 of our clients as
a pilot phase.
But during this time, all changes made the current (old) DB must sync to the new DB AND visa versa. And this should happen real-time.
The structures of the old and new DB will be different - name changes, column changes, table changes, etc.
I was wondering what would be the best way to do this?
The current DB is about 850 GB and is fairly busy, with 1000's of users connected at any time and a big volume of
transactions (reads, write, proc executions...) running all the time.
So whatever means of synch I use, should not have a negative effect on the user experience.
Any suggestions would be appreciated!
Thanks
all systems connecting to it, is being re-designed. Once the new DB and systems are ready, it will go live at 1 of our clients as
a pilot phase.
But during this time, all changes made the current (old) DB must sync to the new DB AND visa versa. And this should happen real-time.
The structures of the old and new DB will be different - name changes, column changes, table changes, etc.
I was wondering what would be the best way to do this?
The current DB is about 850 GB and is fairly busy, with 1000's of users connected at any time and a big volume of
transactions (reads, write, proc executions...) running all the time.
So whatever means of synch I use, should not have a negative effect on the user experience.
Any suggestions would be appreciated!
Thanks