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.

.NET managed provider for Sybase

5 posts in Product Futures Discussion Last posting was on 2002-04-04 20:08:57.0Z
Cosimo Venturella Posted on 2002-03-27 21:18:11.0Z
From: cventurella@fricorporation.com (Cosimo Venturella)
Subject: .NET managed provider for Sybase
Date: Wed, 27 Mar 2002 21:18:11 GMT
Organization: FRI Corporation
Message-ID: <3ca2331a.20868807@forums.sybase.com>
X-Newsreader: Forte Free Agent 1.21/32.243
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 19
NNTP-Posting-Host: 216.13.44.130
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:597
Article PK: 94121

Is anyone aware (or care about) of any a native .NET library to access
a Sybase installation ? by any Organization ?

I am in DataDirect's Connect.NET BETA eval program, but it may be some
time before a version goes gold.

I guess the next question is would Sybase FREELY ship any supposed
.NET "driver" in a future installation ?

I am developing .NET applications using the .NET managed provider for
Ole DB and would like to use ASE 12.5.x on the back-end... everything
works fine with ASE 11.9.2.1 (except for some issue with input
datetime parameters losing 3 milli-seconds), however stored procedure
execution under 12.5 is not functioning correctly.

Anyway, sorry for the side-track... just some history...
cos


Sethu Posted on 2002-03-28 20:05:41.0Z
Message-ID: <3CA37795.BEAD33E0@sybase.com>
Date: Thu, 28 Mar 2002 12:05:41 -0800
From: Sethu <sethu@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Cosimo Venturella <cventurella@fricorporation.com>
Subject: Re: .NET managed provider for Sybase
References: <3ca2331a.20868807@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 23
NNTP-Posting-Host: 10.22.91.118
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:587
Article PK: 94110

Could you pls. send me email what exactly is not
working correctly in 12.5 ?

Thanks,
Sethu

Cosimo Venturella wrote:
>
> Is anyone aware (or care about) of any a native .NET library to access
> a Sybase installation ? by any Organization ?
>
> I am in DataDirect's Connect.NET BETA eval program, but it may be some
> time before a version goes gold.
>
> I guess the next question is would Sybase FREELY ship any supposed
> NET "driver" in a future installation ?
>
> I am developing .NET applications using the .NET managed provider for
> Ole DB and would like to use ASE 12.5.x on the back-end... everything
> works fine with ASE 11.9.2.1 (except for some issue with input
> datetime parameters losing 3 milli-seconds), however stored procedure
> execution under 12.5 is not functioning correctly.
>
> Anyway, sorry for the side-track... just some history...
> cos


Cosimo Venturella Posted on 2002-04-04 20:08:57.0Z
From: cventurella@fricorporation.com (Cosimo Venturella)
Subject: Re: .NET managed provider for Sybase
Date: Thu, 04 Apr 2002 20:08:57 GMT
Organization: FRI Corporation
Message-ID: <3cacb090.22813233@forums.sybase.com>
References: <3ca2331a.20868807@forums.sybase.com> <3CA37795.BEAD33E0@sybase.com>
X-Newsreader: Forte Free Agent 1.21/32.243
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 43
NNTP-Posting-Host: 216.13.44.130
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:558
Article PK: 94088


On Thu, 28 Mar 2002 12:05:41 -0800, Sethu <sethu@sybase.com> wrote:

>Could you pls. send me email what exactly is not
>working correctly in 12.5 ?
>
>Thanks,
>Sethu
>
>Cosimo Venturella wrote:
>>
>> Is anyone aware (or care about) of any a native .NET library to access
>> a Sybase installation ? by any Organization ?
>>
>> I am in DataDirect's Connect.NET BETA eval program, but it may be some
>> time before a version goes gold.
>>
>> I guess the next question is would Sybase FREELY ship any supposed
>> NET "driver" in a future installation ?
>>
>> I am developing .NET applications using the .NET managed provider for
>> Ole DB and would like to use ASE 12.5.x on the back-end... everything
>> works fine with ASE 11.9.2.1 (except for some issue with input
>> datetime parameters losing 3 milli-seconds), however stored procedure
>> execution under 12.5 is not functioning correctly.
>>
>> Anyway, sorry for the side-track... just some history...
>> cos

hi there,

what is not working correctly in 12.5 :

- 1 - i am executing an SP with a datetime output parameter...
- 2 - i have defined the OleDbParameter with OleDbType.DBTimeStamp...
- 3 - when i execute OleDbDataReader =
OleDbCommand.ExecuteReader(CommandBehavior.SingleRow) ,
- or -
- 3 - when i execute OleDbCommand.ExecuteNonQuery() , i get an error
message which goes something like this :

the DateTime data value overflows the type data value in the
consumer's buffer.

hope this will shed some light on this issue,
cos

BTW changing the SP to return varchar(64) output where the date is
converted as convert(varchar(64), <date>, 109) makes nothing work !!!


George Saylor Posted on 2002-03-28 22:18:45.0Z
From: "George Saylor" <gmsayloriii@email.msn.com>
References: <3ca2331a.20868807@forums.sybase.com> <3CA37795.BEAD33E0@sybase.com>
Subject: Re: .NET managed provider for Sybase
Date: Thu, 28 Mar 2002 17:18:45 -0500
Lines: 109
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <PGScGaq1BHA.333@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: tow9dhcp209.towson01.md.comcast.net 68.33.9.209
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:586
Article PK: 94108

here is some background from MSDN <written by Dino Esposito>

OLE DB and "Managed" Providers

ADO .NET does not directly support OLE DB providers, but this doesn't mean
that you cannot access OLE DB providers from ADO .NET. By that, I simply
mean that a special managed provider always pre-processes any incoming calls
aimed to access any existing and valid OLE DB provider. To this end, your
ADO .NET code never directly acts as an OLE DB consumer.
A managed provider is a kind of module that works in .NET in much the same
way an OLE DB provider does in a Win32® and COM environment. Managed
providers are, by all means, the .NET counterpart of OLE DB providers. They
are simpler components and don't have to comply with a complex and somehow
universal specification (remember Universal Data Access?) like OLE DB
providers.
More importantly, managed providers are thought to work entirely within the
context of the .NET Common Language Runtime (CLR). An OLE DB provider is, by
contrast, a plain old COM object that, in a .NET scenario, can only run in
an unmanaged window.
To access the data in ADO .NET, you follow the same sequence of steps as in
a typical ADO session. First off, you create a connection and indicate the
arguments through a connection string. Next, you instantiate a command
object, set the proper command text and behavior, and execute it. Finally,
according to the expected output of the command, either you manipulate the
results or close the connection and go with the remainder of the
application.
Notice that in ADO you could somewhat shorten this sequence and, for
example, call Execute directly on the Connection object. This practice is
simply disallowed in ADO .NET as the various flavors of Connection objects
available don't feature such an Execute method.
Various flavors of Connection objects? What does that mean?
ADO .NET requires you to know and specify in advance, already at connection
time, the type of (managed) data provider you're going to target. In ADO,
you have just one breed of Connection object and that was that, irrespective
of the physical channel used to get or set data. Whether you use OLE DB, or
boil down to ODBC through the generic OLE DB provider for ODBC, ADO always
asks to use the same type of Connection object. This is no longer the case
with ADO .NET.
As of today, you have two different flavors of managed providers. One is
specific for SQL Server 7.0 and 2000, and the other is for accessing any OLE
DB provider. Behind this managed provider, it's easy to recognize the same
design pattern that in ADO allows ODBC data sources access the OLE DB way.
A third managed provider aimed to access ODBC data sources is currently in
beta testing. The managed provider for OLE DB, in fact, does not support the
MSDASQL OLE DB provider that you use in ADO to talk to ODBC drivers.
The SQL Server managed provider defines its classes in the
System.Data.SqlClient namespace. The OLE DB managed provider has its
headquarters in System.Data.OleDb.
In ADO .NET you don't have a generic, but usable Connection class. There is
a DBConnection class which other provider-specific connection classes
inherit from, but that's an abstract class. It is good for prototyping, but
not directly usable in applications.
So to open a connection, you have to use one of the following two methods:
SqlConnection and OleDbConnection. You use the former if you're targeting
SQL Server 7.0, SQL Server 2000, or higher. You would use the latter if
you're destination is an OLE DB provider. You'll use the connection class of
the ODBC .NET provider (called OdbcConnection) if you still need to access
data through an ODBC driver.
To access SQL Server databases using the direct managed provider results in
a much more efficient code. Notice, though, that if you need to access SQL
Server 6.5, then you must resort to the OLE DB provider and use the OleDbXxx
classes and the managed provider for OLE DB.
So, in ADO .NET you have a lot of dual classes like SqlConnection and
OleDbConnection, SqlCommand and OleDbCommand, SqlDataReader and
OleDbDataReader, and so on. While the biggest difference between the various
pairs is probably still in the prefix, it would be incorrect to state that
they are all equal as for the programming interface.
For sure, each pair of classes does mostly the same thing, but their overall
interface reflects the underlying data provider. For example, you won't find
a Provider property on the SqlConnection object, and there will be no notion
of PacketSize or WorkStationId in an OleDbConnection class.
In the remainder of this article, I'll be using the SQL Server managed
provider, which means my data-oriented ADO .NET classes will generally have
a Sql prefix. The previous disclaimer withstanding, the code should work
unchanged, or with limited changes, also for data sources exposed by OLE DB
providers.


George

"Sethu" <sethu@sybase.com> wrote in message
news:3CA37795.BEAD33E0@sybase.com...
> Could you pls. send me email what exactly is not
> working correctly in 12.5 ?
>
> Thanks,
> Sethu
>
> Cosimo Venturella wrote:
> >
> > Is anyone aware (or care about) of any a native .NET library to access
> > a Sybase installation ? by any Organization ?
> >
> > I am in DataDirect's Connect.NET BETA eval program, but it may be some
> > time before a version goes gold.
> >
> > I guess the next question is would Sybase FREELY ship any supposed
> > NET "driver" in a future installation ?
> >
> > I am developing .NET applications using the .NET managed provider for
> > Ole DB and would like to use ASE 12.5.x on the back-end... everything
> > works fine with ASE 11.9.2.1 (except for some issue with input
> > datetime parameters losing 3 milli-seconds), however stored procedure
> > execution under 12.5 is not functioning correctly.
> >
> > Anyway, sorry for the side-track... just some history...
> > cos


Jim Egan Posted on 2002-03-28 04:47:29.0Z
From: Jim Egan <dontspam.dbaguru@eganomics.com>
Subject: Re: .NET managed provider for Sybase
Date: Wed, 27 Mar 2002 21:47:29 -0700
Message-ID: <MPG.170c4e48eaa24ec398bc95@forums.sybase.com>
References: <3ca2331a.20868807@forums.sybase.com>
Reply-To: eganjp@compuserve.com
X-Newsreader: MicroPlanet Gravity v2.50
Newsgroups: sybase.public.ase.product_futures_discussion
Lines: 30
NNTP-Posting-Host: 12-252-108-115.client.attbi.com 12.252.108.115
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:595
Article PK: 94120


cventurella@fricorporation.com wrote...
> Is anyone aware (or care about) of any a native .NET library to access
> a Sybase installation ? by any Organization ?
>
> I am in DataDirect's Connect.NET BETA eval program, but it may be some
> time before a version goes gold.
>
> I guess the next question is would Sybase FREELY ship any supposed
> NET "driver" in a future installation ?
>
> I am developing .NET applications using the .NET managed provider for
> Ole DB and would like to use ASE 12.5.x on the back-end... everything
> works fine with ASE 11.9.2.1 (except for some issue with input
> datetime parameters losing 3 milli-seconds), however stored procedure
> execution under 12.5 is not functioning correctly.
>
> Anyway, sorry for the side-track... just some history...

Sybase has been gathering interest in .NET drivers. I have relayed to the person
interested in this that there have been an increasing number of questions related to
accessing ASE from .NET applications. Putting in a call to Tech Support and requesting
this wouldn't hurt.
--
Jim Egan [TeamSybase]
Senior Consultant
Sybase Professional Services