|
I don't see anything that looks odd. I guess CREATE INDEX can't be created with NC? On 1/16/07, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
Try this again. But run STRDBG UPDPROD(*YES) before you do a STRSQL. When you exit STRSQL do a DSPJOBLOG and see if anything sticks out. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Michael Ryan" <michaelrtr@xxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/16/2007 08:30 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <MIDRANGE-l@xxxxxxxxxxxx> cc Subject COMMIT Needed? I had a process where I did an INSERT with NC into a table. It took over 5 minutes. I then did a CREATE INDEX, the same INSERT, and a DROP INDEX. Total time now 45 seconds. Obviously much better. However, when I exited Interactive SQL, I needed to do a COMMIT (or ROLLBACK). I determined it was as a result of the CREATE INDEX. Why is that? Thanks... -- 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 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.