RE: sql - Drop and Add constraints

[PatrickConner@xxxxxxxxxxxxxxxxx]

Patrick,

Is anything happening between the clearing of the file and the second
RUNSQLSTM which repopulates Table1?  Or is Table1 empty when the
constraints get put back?

** No. Table1 is empty.

If Table1 is populated when the constraints are added back, is the size
of Table2 relatively constant or has it increased significantly over
time?

** All files are empty at the time the constraints are added back

Has anything happened over time to increase the number of indexes built
over Table1?

** No. These files are not allowed any more indexes (by design).
** In other words, I'm the only one that works in this library and I
haven't added any indexes.

Regards,
Andy Nolen-Parkhouse

> We have a process that drops the constraints on tables (physical
files),
> clears them with a CLRPFM, and then rebuilds the constraints.
> At first this process took 20 minutes. Now it takes 2 1/2 hours. My
> question is why? or how is this possible?
>
> Here is a small sample:
>
> RUNSQLSTM  SRCFILE(SourceLib/SourceFile) SRCMBR(Member1) +
>              NAMING(*SQL) DFTRDBCOL(DataLib)
>
> CLRPFM     FILE(Table1)
> .
> .
>
> RUNSQLSTM  SRCFILE(SourceLib/SourceFile) SRCMBR(Member2) +
>              NAMING(*SQL) DFTRDBCOL(DataLib)
>


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.