MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2012

Re: Index Advisor Recommending EVI



fixed

Everything in our "production" environment also goes change control...

However, there's production and then there's production :)

While I can't manually change anything in the PROD_DATA or PROD_PGM
libraries, I do have my own work library on the production machine. I
can put an index for a production table in my work library. The
system can always find indexes and use them wherever they are, no
matter whom owns them or what the authority set on them is.

Given that the production system is the only place I can truly tune
SQL under production conditions, being able to create indexes
temporarily and see what effect they have is invaluable. Once I
decide the index is useful, I'll define it to our CMS and have it
pushed to production normally at which point I can delete my temporary
one; if I hadn't already.

Charles

On Thu, Mar 15, 2012 at 8:56 AM, Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx> wrote:
Moot point in my case.  Because everything in our production environment
has to go through change control, I am creating SQL source for each index I
create.  Any changes to the underlying table will result in all the indexes
being recreated anyway.

I am naming them in such a way that I know they were created for SQL and
not to expect any program references (not that there's anything wrong with
that).


Gord





On Wed, Mar 14, 2012 at 3:53 PM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:

This is true, but there are ways not to be affected too badly. Actually
you can simply use CHGPF and specify the DDS source, the system will
take care of the logicals for you. Same as ALTER TABLE, basically.

Vern

On 3/14/2012 2:04 PM, ALopez@xxxxxxxxxx wrote:
-snip-

Because the logicals you create will also need to be removed if
someone else wants to modify the physical file,
-snip-
--
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.




--
Gord Hutchinson
TST Overland Express
--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact