Features of SNC SQL Native Client vs OLEDB vs ADO.NET

[Viswa]

We have migrated our application in PowerBuilder 9 to
PowerBuilder 11. PB 9 worked well with SNC Native Client
driver. Thinking to use ADO.NET or OLEDB instead. If we get
any sort replies related to comparision, features and
connectivity that could be immense useful

[Jim O'Neil [Sybase]]

PoweBuilder 9 didn't have the SNC native driver??? Did you mean the
MSS native driver in PB9?

[Chris Pollach]

V;

NO ...

1) PB 9 used the "MSS" setting which invoked the ntdblib.dll MS db driver.
(MS [idiots] deprecated that in SS2005!
2) PB 11 supports the new SNC db driver from MS.
- Note only works with SS2K and 2005 or higher.

Note that MS has stated that new features like async operations, new
isolation levels, MARS (multiple active result sets), etc will *only* be
supported in the future with SNC. SNC is actually a "fast path" through
OLE-DB. Personally - I would suggest that you look at this mechanism for
your standard DB access to SS.

--
Regards ... Chris
http://chrispollach.pbdjmagazine.com
,\|/,
(0 0)
-(_)-

<Viswa> wrote in message news:4795075e.26b...@sybase.com...

[Tyler Cruse]

There has been some benchmarks done and so far there are fairly large
differences in the conclusions.

For OLE_DB there are two approaches 1) using SQLOLEDB as provider or 2)
SQLNCLI as provider
( My opinion is that SQLNCLI works slightly faster and makes more sense
since SQLOLEDB provider is also provided by the SQLSNC code) Both of these
use odbc110.ini file for parameters, if "ServerCursor = NO" is not included
or the ini file not deployed with your executable performance will be bad
(sometimes very bad).

PB SNC - uses OLE_DB calls to the database, provides a cleaner interface
for PB applications (and probably easier to use). DBParam keywords are
different but close to OLE_DB keywords. Does not use PBODB110.ini file.

ADO - takes more memory on client machine, takes more CPU resources on
client machine. Sometimes additional caching will provide quicker access to
data. Seems to be stable and reliable. Makes more sense when used with
other MS dot net code. (e.g. datawindow dot net)

ODBC - not recommended except in cases where there is no other choice. When
used over WAN performance is very bad. When used with fast local network
and fast SQL server performance is OK

My personal preference for PB applications is SNC.

[Chris Pollach]

Hi Ty;

Yes, that is basically what I found as well ...

FYI:
http://chrispollach.pbdjmagazine.com/sqlserver2005__who_redesigned_this_release.htm

Regards ... Chris

"Tyler Cruse" <tcr...@trlx.com> wrote in message
news:47989c60$1@forums-1-dub...