RE: ODBC vs OLE DB/400 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: ODBC vs OLE DB/400
From: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
Date: Wed, 5 Apr 2006 11:15:56 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

>My main concern is performance on the iSeries side.

As long as you're talking "normal" OLEDB and not the iSeries specific
Record Level Access stuff. (Normal means you're just doing select,
insert, update, delete, call, etc.) then on the iSeries side the all
(ODBC, OLEDB, JDBC and .NET) go through the same QZDASOINIT engine so it
shouldn't matter.

In general any performance issues with remote data access are related to
poor sql coding or poor index tuning on the iSeries side and not to the
connection path. 

-Walden

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.