FreeTDS Development Group

[PMoore AT axa.com.au]

hehe...well it _is_ MS i guess ;-) but it all depends on what you are doing
and storing.
database contention is not nice....

if the connection info stored in this database points to different servers
then i'd say you'd have to add them to the FreeTDS conf/interfaces file.
I'm only going on my Sybase experience here and if you are using OpenClient
to connect to a server then it needs to read the info from the interfaces
file. If the info isn't there you get a Sybase error:

Open Client Message
Layer 5, Origin 3, Severity 5, Number 4
OS Error: TLI rcvconnect call failed - t_errno 9
ct_connect(): network packet layer: internal net library error: Net-Lib 
protocol driver call to connect two endpoints failed

Basically this means that it couldn't connect to the server.
I'll have a think on some possible workarounds.
regards
peter






James Cameron <cameron AT stl.dec.com>@franklin.oit.unc.edu on 12/07/2001
08:51:21 AM

Please respond to "TDS Development Group" <freetds AT franklin.oit.unc.edu>

Sent by:  bounce-freetds-132908 AT franklin.oit.unc.edu


To:   "TDS Development Group" <freetds AT franklin.oit.unc.edu>
cc:
Subject:  [freetds] Re: Genereic db connection


PMoore AT axa.com.au wrote:
> i'm assuming the databases all live on the one server......

What a novel idea!  ;-)

No, different servers.  One huge server isn't big enough, and anyway,
that creates a single point of failure for multiple databases.  I'd
never want to do that for mission critical stuff.

--
James Cameron

---
You are currently subscribed to freetds as: [PMoore AT axa.com.au]
To unsubscribe, forward this message to
$subst('Email.Unsub')










**********************************************************************
Important Note
This email (including any attachments) contains information which is 
confidential and may be subject to legal privilege.  If you are not 
the intended recipient you must not use, distribute or copy this 
email.  If you have received this email in error please notify the 
sender immediately and delete this email. Any views expressed in this 
email are not necessarily the views of AXA.   Thank you.
**********************************************************************