Attempting to run queries against a SQL database with a 100% availability SLA.
Possible table locks caused by competing calls from third party and native SQL queries. Which may negatively impact SLA
Create a secondary SQL database and sync it to the primary. Then convert the secondary database to a read-only database. Finally configure the SQL databases to run in a disaster recovery mode, meaning that the secondary listens to the primary's heartbeat and switches over to primary role when it detects the primary server is down.
- The SQL servers will run on JDBC 4.0 or higher to leverage the listener feature to allow the disaster recovery architecture
- The third party software running queries against the SQL database should support ALWAYS-ON connection
- The third party software should also have JDBC 4.0 or higher running