Re: Actually using commitment control and QTEMP -- RPG400-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: Actually using commitment control and QTEMP
From: CRPence <crpbottle@xxxxxxxxx>
Date: Wed, 23 Dec 2015 11:52:32 -0700
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 18-Dec-2015 06:30 -0700, darren wrote:

<<SNIP>> Are there really performance improvements to using global
temporary tables, compared to creating a QTEMP/TBL table?

The GTT may actually be slightly [though surely imperceptibly] more expensive, but especially if there is implicit journaling per isolation and\or clause(s) specified; yet if the standard CREATE TABLE QTEMP/... had to effect the journaling, depending on how that was implemented and accounted, then the non-GTT is probably more expensive.

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.