hi All
When redundant server takes over from the master then if 2 way database replication is not set up the history will not be working.
I am familiar with history splitter provider but if transaction manager, scripts or query bindings are used this will not synchronize across master and redundant database.
So to make the redundancy truly working 2 way database synchronisation is essential.
What tools could be used if we assume that microsoft SQL server is used?
Probably more of a database setting depending on your database architecture, we used to configure the databases to handle syncronisation themselves with us just sending the data into one or the other depending on which was actually alive.
Splitter I've found is good if you have for example a local database for you to use and a parallel remote server database
2 Likes
history splitter only does simple job but ignores transactions groups, scripts and query binding updates to the database hence full 2 way database synch is essential for the redundancy to make sense
Yeah so only use case we had was another department wanted to see all of historical data for another side-project. So we gave them a seperate database and split the data for them to use.