SQL failover partner

[STOps9487]

In Tidal Scheduler, we can configure a failover SQL partner so that if the primary SQL server is not available, it will automatically try to connect to a failover partner.          

For JDBC, you can use "failoverPartner=xxxxxxxx"

Is there something similar we can use for Orchestrator?

I notice in Tidal.Automation.Server.exe.config there is a database properties setting, which has a field called "connectionString"

       connection string='Data Source=XXXXXXXXXXX;Initial Catalog=TEOProcess;Integrated Security=False;MultipleActiveResultSets=True;Max Pool Size=500;'

Can this connection string be modified to add a failover server for a mirrored database environment in either CPO 2.3 or 3.0?

[Svetlana Kryukova]

Instead of using "custom" failover solution on the database side, you should be using industry standards: SQL Failover Cluster or Oracle RAC.

CPO 3.0 supports both for Process and Reporting database. TEO 2.3 support both for Process database, and SQL Failover Cluster only for Reporting.

[STOps9487]

For whatever reason, our DB team are no longer doing DB clusters. They are doing mirroring - this is why the other method is required.

Anyway, apparently with SQL 2012 they are going to use clusters again, so as long as CPO 3.0 can use SQL 2012 we should be OK.

[Shaun Roberts]

CPO 3.0 supports both Windows 2012 and SQL 2012. I use them both on multiple instances.