|
Walden, We're doing a lot of reporting using Crystal Reports & ODBC. Some of the SQL statements are rather nasty. The UI is web driven; I'm not entirely sure of all of the technologies involved. It's had performance issues on occasion so I'm always on the lookout for anything that might be of use to improve our situation. Our non-iSeries developers are pretty good at SQL/SQL Server, and do a lot of .NET and VB stuff. No real Java, though. I'm mostly wondering if .NET would be better that ODBC from a performance standpoint. But if everything passes through QZDASOINIT the point may well be moot. Thanks, John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich Sent: Wednesday, April 05, 2006 10:13 AM To: Midrange Systems Technical Discussion Subject: RE: ODBC vs OLE DB/400 John, Using them from where? Some applications want to talk to OLEDB drivers, some to ODBC drivers. If you're speaking of programming, in what? If it's something .NET then you don't want to use either, you want to use the .NET native provider from IBM. If you're using older COM based connections (VB6, Delphi, PB, etc.) then it almost doesn't matter. Code to ADO for data access and you can switch between the two in the connection string. I've seen some reports in the past that showed ODBC w/a slight advantage on first-connect and inserts and OLEDB w/an advantage on larger recordsets, but in general it's a wash. -Walden -- Walden H Leverich III Tech Software (516) 627-3800 x3051 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in future then please respond to the sender to this effect.
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.