Hi Mike,
Considering two SQL-servers (primary and backup) in a high availability
environment:
<AuthBy SQL>
# Our main SQL server details
DBSource dbi:xxx:xxx
DBUsername ????
DBAuth ??
# Fallback SQL server details
DBSource dbi:yyy:yyy
DBUsername ????
DBAuth ??
...
</AuthBy>
If I understand correctly: after the primary SQL-server fails Radiator
connects to the back-up SQL-server. Radiator remains connected to this
server until it fails and then tries to reconnect to the primary SQL-server.
I wonder if there is a way to force Radiator to reconnect to the primary
SQL-server, once it has become available again? To implement this Radiator
should periodically check the availability of the SQL-servers.
Cheers,
Alexander de Boer
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
