Setting a Fail-Over Connection String
- 16 Jun 2022
- 1 Minute to read
- Print
- DarkLight
Setting a Fail-Over Connection String
- Updated on 16 Jun 2022
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
When SQL Server replication is configured, Decisions will automatically route to a Secondary Database in the event of failure in the Primary Database. Otherwise, when data is added to the Primary Database, it copies that data to another database that is not on the same server.
Such secondary connections can be established after installation via the Decisions Installer's Settings.
Restore To Primary Database
If the server trips the secondary connection, this would create a UsingFailoverConnection.txt file. In order to restore the connection to the primary database, this file must be deleted at C:\Program Files\Decisions\Decisions Server\Instances\Control\Database\UsingFailoverConnection.txt
Example
- Download and open DecisionsServerInstaller.exe from Decisions Releases.
From the Decisions Installer, click EDIT SETTINGS.
From the Settings window, locate SecondDatabaseConnectString.
Provide the desired ConnectString, this can lead to an alternate database on the same server, ie., changing the Initial Catalog value to match a database that exists in MSSQL called "decisionsalt", or it may be the same as the value found in DatabaseConnectString.
Then, click Save and close the installer.
For further information on Administration, visit the Decisions Forum.
Was this article helpful?
