Skip to Content.
Sympa Menu

freetds - RE: RE: [freetds] ASA Error -83: Specified database not found

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: RE: [freetds] ASA Error -83: Specified database not found
  • Date: Thu, 27 Feb 2003 17:02:31 -0500

> From: Brian Bruns [mailto:camber AT ais.org]
> Sent: February 27, 2003 4:20 PM
>
> this is not a
> problem when using ASA 5.5 with OSG, just with native support
> under 6.0 (and higher I presume).

The older product works correctly? Only ASA 6.0+ insists we pass the
database name in the lservname login packet? Thanks for looking into this.


> The problem is that the database *is* the server
> name under ASA. That is, if you have two databases you have
> two services under Win32.

Same port? Does "select @@servername = db_name()" always returns 1?

> I'd reccommend having a servername = blah entry in the
> freetds.conf that
> defaults to the [] name and is sent with the login
> packet...no need for
> special ASA logic, it can be used globally. Sending the alias name
> isn't always the best strategy. I'll try to wrap up a patch
> like this if it sounds good. 0.62 fodder...

I don't like that idea very much; I think it's too open-ended. It's hard
enough to get folks to understand the ip->hostname->servername relationship
(particularly given the odd use of "hostname" -- i.e. client workstation's
claimed name -- in the vendor docs). The smart folks would ignore a
"servername" line; the lucky ones would set it to the [] name; and the rest
would write to the list wondering what to do. Of course, some people would
spend time in more than one category....

I think it would be better to have an optional "server type" entry. The
domain would be Vendor-[Model-]version:

Microsoft-[6.5 | 7.0 | 2000]
Sybase-[10 | 11 | 12.5]
Sybase-ASA-[5.5 | 6.0 | ...]

This lets us do server-specific processing and/or consistency checking:

A. Trivially, for example, we could verify that the stated server type
supports the requested TDS version before attempting to connect.

B. In this case, we could swap in the dbname, if provided, for the
servername in lsrvname if the servertype is in out ASA list.

C. If there's a servertype and no tds version specified, we could make a
reasonable choice based on the server type instead of falling back on
--with-tds-version.

Granted, "server type" places the onus on us. It's no more work to parse
out of the file, but it forces us to decide what to do based on the value.
OTOH, it moves from prescription to description, which on the whole is
easier to support and use.

Could you get behind that?

(Also, I was hoping to hear from you re AIX and rc5.)

Best regards old man,

--jkl



The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.





Archive powered by MHonArc 2.6.24.

Top of Page