|
>SQL works great for result sets but I would have a hard time >believing that single record SQL access is as fast as RPG >native DB access. Maybe things have changed and my brain data is old though. I'm a SQL lover, but I think it's been shown over and over that there are cases where "native" IO blows the doors of SQL. HOWEVER, you must also take a step back and look at the problem from a different point of view. I've seen cases where SQL was substituted for a CHAIN or a SETLL/READE and it was "shown" that the result was slower than the native IO. But the real question is, would you have even needed that CHAIN if you'd looked at the problem from a SQL point of view and used a join? Or would you need to read all those records if you looked at the problem from a SQL point of view and used a "sum(fld1) group by fld2" SQL statement. SQL is damn fast in set oriented tasks, the real trick is to see if you can rework the initial question to be set oriented instead of trying to make SQL solve a problem that's not set oriented. SQL really doesn't mind 10-way joins w/subselects, and sometimes that's how you need to look at the problem. -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.)
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.