| Title: | SQL/Services Forum |
| Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) |
| Moderator: | SQLSRV::MAVRIS |
| Created: | Thu Oct 13 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2214 |
| Total number of notes: | 8586 |
I got a question concerning fail-over. Eg. the simplest form of
fail-over: Manually reconnect to the same datasource. As far as I know
there is no way to configure ODBC to point to a service that exists on
more than one server.
I know that this possibillity exist in SQL*net v2+. Will that work
SQL/Services V7.0 or am I missing something.
/uw
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2162.1 | Yup - you can use SQL*Net and specify an address list | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Wed Mar 12 1997 18:15 | 12 |
SQL*Net allows you to specify address lists. If you connect to a SQL*Net service on one node in the address list, and that node fails, your next connect attempt will use the next working node in your address list. If that's what you mean, then yes, you can get this behavior with SQL/Services 7.0 using SQL*Net as a transport. From ODBC or a SQL/Services client, you specify a SQL*Net service name. That SQL*Net service name can resolve to a list of SQL/Services service names on different nodes where each SQL/Services service connects to the same database. Sue | |||||
| 2162.2 | Yes | 4177::UWAHLQVI | Fri Mar 14 1997 10:59 | 5 | |
Sue,
That is exactly what I mean.
/uw
| |||||