Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Sybase 11 and Intersolv ODBC 3.0

4 posts in Windows NT Last posting was on 1999-03-03 15:56:45.0Z
Allan Taunt Posted on 1997-06-29 06:40:16.0Z
From: "Allan Taunt" <ataunt@swichtec.co.nz>
Subject: Sybase 11 and Intersolv ODBC 3.0
Organization: Swichtec Power Systems
Message-ID: <01bc8461$235294c0$010aa8c4@capricorn>
X-Newsreader: Microsoft Internet News 4.70.1157
Newsgroups: sybase.public.sqlserver.nt
Date: Sun, 29 Jun 1997 02:40:16 -0400
Lines: 27
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5596
Article PK: 1081673

Dear All,

Does anyone use Sybase Server 11 (11.0.2.1) with Intersolv's ODBC version
3.0 drivers. I have this setup on Windows NT 4.0 Server (Service Pack 2)
and I get an error message saying that stored procedure Sp_SeRvEr_InFo not
found (note the case!!). This error occurs with both MSQuery32 and Visual
Basic 5.0. I have found this error only occurs when I specify the database
when connecting (if it is not specified, that is the default is used there
is no problem connecting even the default is the same as the one I was
specifying). Another thing to note is this problem does not occur with the
Intersolv 2.12 drivers. When I connect with WISQL or Intersolv 2.12
drivers I can quite happily execute the stored procedure sp_server_info
without any problem.

To summarise:
Sybase Server 11 (11.0.2.1) and Intersolv ODBC Drivers 3.0 produce the
error Sp_SeRvEr_InFo not found when a database is specified when
connecting.

Any help appreciated

Allan Taunt

Global Information Solutions
Christchurch
New Zealand


T Schantz Posted on 1997-08-22 05:52:56.0Z
Message-ID: <33FD2938.7934@pop.ultranet.com>
Date: Thu, 21 Aug 1997 22:52:56 -0700
From: T Schantz <schantz@pop.ultranet.com>
Reply-To: "schantz[NO-SPAM]"@schantz.ultranet.com
Organization: MAPPIT
X-Mailer: Mozilla 3.0 (Win16; U)
MIME-Version: 1.0
To: Allan Taunt <ataunt@swichtec.co.nz>
Subject: Re: Sybase 11 and Intersolv ODBC 3.0
References: <01bc8461$235294c0$010aa8c4@capricorn>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 38
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5568
Article PK: 1081646


Allan Taunt wrote:
>
> Dear All,
>
> Does anyone use Sybase Server 11 (11.0.2.1) with Intersolv's ODBC version
> 3.0 drivers. I have this setup on Windows NT 4.0 Server (Service Pack 2)
> and I get an error message saying that stored procedure Sp_SeRvEr_InFo not
> found (note the case!!). This error occurs with both MSQuery32 and Visual
> Basic 5.0. I have found this error only occurs when I specify the database
> when connecting (if it is not specified, that is the default is used there
> is no problem connecting even the default is the same as the one I was
> specifying). Another thing to note is this problem does not occur with the
> Intersolv 2.12 drivers. When I connect with WISQL or Intersolv 2.12
> drivers I can quite happily execute the stored procedure sp_server_info
> without any problem.
>
> To summarise:
> Sybase Server 11 (11.0.2.1) and Intersolv ODBC Drivers 3.0 produce the
> error Sp_SeRvEr_InFo not found when a database is specified when
> connecting.
>
> Any help appreciated
>
> Allan Taunt
>
> Global Information Solutions
> Christchurch
> New Zealand

Look at the readme file that came with intersolv/ sybase
3.0 odbc driver.
there is a set of scripts that is provided. one is for
4.x and the other for 10.x plus servers. The files
can be read with a text editor, try searching for
the sp in there. They are for 3.0 odbc compliance
but may have an affect on what you are seeing
maybe.....
ted


Robert Eckert Posted on 1997-09-04 14:25:46.0Z
Message-ID: <340EC4E9.95F8922@mail.mitchell.net>
Date: Thu, 04 Sep 1997 09:25:46 -0500
From: Robert Eckert <reckert@mail.mitchell.net>
Reply-To: reckert@superlink.net
X-Mailer: Mozilla 4.0 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Re: Sybase 11 and Intersolv ODBC 3.0
X-Priority: 3 (Normal)
References: <01bc8461$235294c0$010aa8c4@capricorn> <33FD2938.7934@pop.ultranet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 58
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5557
Article PK: 1081632


T Schantz wrote:

> Allan Taunt wrote:
> >
> > Dear All,
> >
> > Does anyone use Sybase Server 11 (11.0.2.1) with Intersolv's ODBC
> version
> > 3.0 drivers. I have this setup on Windows NT 4.0 Server (Service
> Pack 2)
> > and I get an error message saying that stored procedure
> Sp_SeRvEr_InFo not
> > found (note the case!!). This error occurs with both MSQuery32 and
> Visual
> > Basic 5.0. I have found this error only occurs when I specify the
> database
> > when connecting (if it is not specified, that is the default is used
> there
> > is no problem connecting even the default is the same as the one I
> was
> > specifying). Another thing to note is this problem does not occur
> with the
> > Intersolv 2.12 drivers. When I connect with WISQL or Intersolv 2.12
>
> > drivers I can quite happily execute the stored procedure
> sp_server_info
> > without any problem.
> >
> > To summarise:
> > Sybase Server 11 (11.0.2.1) and Intersolv ODBC Drivers 3.0 produce
> the
> > error Sp_SeRvEr_InFo not found when a database is specified when
> > connecting.
> >
> > Any help appreciated
> >
> > Allan Taunt
> >
> > Global Information Solutions
> > Christchurch
> > New Zealand
> Look at the readme file that came with intersolv/ sybase
> 3.0 odbc driver.
> there is a set of scripts that is provided. one is for
> 4.x and the other for 10.x plus servers. The files
> can be read with a text editor, try searching for
> the sp in there. They are for 3.0 odbc compliance
> but may have an affect on what you are seeing
> maybe.....
> ted

Actually this is a bug in the ODBC driver, my company has done
extensive testing of this ODBC driver and found severe problems. One of
which is that Sp_SeRvEr_InFo problem. We finally wound up using the
ODBC driver from a company called Simba, you can download the driver
from www.simbatech.com. While we still have a few issues to work
through with them, they are much more responsive than Intersolv. The
one thing they do not currently support is dynamic cursors, which if you
use the Microsoft ODBC cursor library, the application won't notice.
They do have much better performance on queries also.

Rob Eckert
Sr Systems Analyst
Teleport Communications Group
eckertrw@tcg.com


Jim Lee Posted on 1999-03-03 15:56:45.0Z
Message-ID: <36DD5BBD.FAFC4AE3@mail.tea.state.tx.us>
Date: Wed, 03 Mar 1999 09:56:45 -0600
From: Jim Lee <jlee@mail.tea.state.tx.us>
Organization: Texas Education Agency
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Sybase 11 and Intersolv ODBC 3.0
References: <01bc8461$235294c0$010aa8c4@capricorn> <33FD2938.7934@pop.ultranet.com> <340EC4E9.95F8922@mail.mitchell.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 75
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:4078
Article PK: 1091463

There are EBF's for the ODBC 3.0 driver. Also, within the ODBC 3.0 patches
are fixes to the catalog stored procedures for the server. Sybase has
released two patches for CSP's, which is the sycsp11.sql file under the
"odbc" sub-directory of the ODBC EBF. There is no version number on the
sycsp11.sql file, but it is possible to distinguish by datetime and file
size. The last CSP fix I installed was the sycsp11.sql file from 6/22/98
with a file size of 114 KB. This particular sycsp11.sql is in the ODBC
11.1.1 EBF 8315.

Robert Eckert wrote:

> T Schantz wrote:
>
> > Allan Taunt wrote:
> > >
> > > Dear All,
> > >
> > > Does anyone use Sybase Server 11 (11.0.2.1) with Intersolv's ODBC
> > version
> > > 3.0 drivers. I have this setup on Windows NT 4.0 Server (Service
> > Pack 2)
> > > and I get an error message saying that stored procedure
> > Sp_SeRvEr_InFo not
> > > found (note the case!!). This error occurs with both MSQuery32 and
> > Visual
> > > Basic 5.0. I have found this error only occurs when I specify the
> > database
> > > when connecting (if it is not specified, that is the default is used
> > there
> > > is no problem connecting even the default is the same as the one I
> > was
> > > specifying). Another thing to note is this problem does not occur
> > with the
> > > Intersolv 2.12 drivers. When I connect with WISQL or Intersolv 2.12
> >
> > > drivers I can quite happily execute the stored procedure
> > sp_server_info
> > > without any problem.
> > >
> > > To summarise:
> > > Sybase Server 11 (11.0.2.1) and Intersolv ODBC Drivers 3.0 produce
> > the
> > > error Sp_SeRvEr_InFo not found when a database is specified when
> > > connecting.
> > >
> > > Any help appreciated
> > >
> > > Allan Taunt
> > >
> > > Global Information Solutions
> > > Christchurch
> > > New Zealand
> > Look at the readme file that came with intersolv/ sybase
> > 3.0 odbc driver.
> > there is a set of scripts that is provided. one is for
> > 4.x and the other for 10.x plus servers. The files
> > can be read with a text editor, try searching for
> > the sp in there. They are for 3.0 odbc compliance
> > but may have an affect on what you are seeing
> > maybe.....
> > ted
>
> Actually this is a bug in the ODBC driver, my company has done
> extensive testing of this ODBC driver and found severe problems. One of
> which is that Sp_SeRvEr_InFo problem. We finally wound up using the
> ODBC driver from a company called Simba, you can download the driver
> from www.simbatech.com. While we still have a few issues to work
> through with them, they are much more responsive than Intersolv. The
> one thing they do not currently support is dynamic cursors, which if you
> use the Microsoft ODBC cursor library, the application won't notice.
> They do have much better performance on queries also.
>
> Rob Eckert
> Sr Systems Analyst
> Teleport Communications Group
> eckertrw@tcg.com