Skip to Content.
Sympa Menu

freetds - RE: [freetds] Connecting to MS SQL Server

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Tom Wakefield" <tom_wakefield AT nacm.com>
  • To: <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Connecting to MS SQL Server
  • Date: Fri, 31 Jan 2003 07:59:07 -0800

Thanks all,
I will take a look at sqsh.

-----Original Message-----
From: Brian Bruns [mailto:camber AT ais.org]
Sent: Friday, January 31, 2003 7:37 AM
To: freetds AT lists.ibiblio.org
Subject: RE: [freetds] Connecting to MS SQL Server

You want to use sqsh (www.sqsh.org). It's a full featured isql
replacement and then some. tsql is mainly for connectivity testing and
debugging, although it's been gaining more features as time goes on, I'm

not sure what other peoples opinions are of where it's heading.

Brian

On Fri, 31 Jan 2003, Tom Wakefield wrote:

> I guess I should have been more specific on how I was connecting. I
am
> just using tsql command to connect. It is kind of annoying to the
users
> and any shell scripts have to be coded in a way to ignore this when
> connecting to a MS SQL Server (usually skipping the first 3 lines
> returned) and not to when connecting to a Sybase ASE server.
>
> Also, with both Microsoft and Sybase's isql command they have an
option
> of
> -w[column width]. Are there any plans to have this with the tsql
> command?
>
> -----Original Message-----
> From: Thompson, Bill D (London) [mailto:ThompBil AT exchange.uk.ml.com]
> Sent: Friday, January 31, 2003 7:12 AM
> To: 'freetds AT lists.ibiblio.org'
> Subject: RE: [freetds] Connecting to MS SQL Server
>
> Hi Tom,
>
> I guess from looking at the link you've sent that you're using ODBC.
>
> I'm not familiar with ODBC myself, but in other API's (dblibrary for
> example), it is possible to define your own error handlers which the
API
> will call in the event of an error. It is usual to include code which
> filters out these informational messages in your error handler.
>
> The link suggests that this is the correct thing to do in ODBC as
well,
> viz:
>
> "Applications need to code their error handling routines for SQL
Server
> connections to call SQLError() until it returns SQL_NO_DATA_FOUND, and
> act
> on any messages other than the ones that return a pfNative code of
5701
> or
> 5703. "
>
> HTH,
>
> Bill
>
> > -----Original Message-----
> > From: Tom Wakefield [SMTP:tom_wakefield AT nacm.com]
> > Sent: 31 January 2003 15:03
> > To: freetds AT lists.ibiblio.org
> > Subject: [freetds] Connecting to MS SQL Server
> >
> > Question for the group:
> >
> >
> >
> > When connecting to a MS SQL Server (regardless of version) I receive
a
> > MSG 5703.
> >
> >
> >
> > According to MS, a 5703 indicates the language being used on the
> server.
> > Therefore, MS states that you can ignore 5703; since it is
> informational.
> > See Microsoft Knowledge Base Article - 143339.
> > (http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b143339)
> >
> >
> >
> > So from a configuration of FreeTDS is there any way of suppressing
MSG
> > 5703.
> >
> >
> >
> >
> >
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
>

_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds




Archive powered by MHonArc 2.6.24.

Top of Page