Instead of having index adviser create the index for you, use the "Show SQL" option in the drop down(At V7 it's the third item) You will see output like: (I just picked this one because it was near the top, it's an example)

/* Creating index BPCS6F.IIM_INDEX_00001
When creating this index the database connection should have a sort sequence of *HEX.

-- System name:
-- Database: myhost Advised Indexes for myhost
-- Times Advised for Query Use: 6110480
-- First Advised: 7/22/12 8:05:44 PM
-- Last Query Use: 12/4/12 5:24:37 AM
-- Reason Advised: Row selection
-- Estimated Index Creation Time (seconds): 00:00:05
-- Rows in Table when Advised: 95434
-- Average of Query Estimates (seconds): 0.0001
-- Most Expensive Query Estimate (seconds): 3
-- Index Type Advised: Not unique */

/* Setting label text for BPCS6F.IIM_INDEX_00001 */
LABEL ON INDEX BPCS6F.IIM_INDEX_00001 IS 'Index generated from Index Advisor';

You can strip out or modify the comments as needed. I also tend to change the names of the indices to indicate what they index, and change the text. Makes it much easier when you start getting a bunch of index objects out there.

Now you can put the SQL into a source member and allow your change control process to do its thing.....

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 12/3/2012 8:32 PM, Sam_L wrote:
Index Advisor makes it very easy to create new SQL indexes. However, I
have to add them to Aldon LMi, either as a non-source object, or create
the source and use the same approach as with DDS.

Any Aldon users with an opinion pro or con?

The non-source object approach is the easiest but I have this hankering
for source under source control... I can get the source back from Index
Advisor, but then I have to hand tweak it to fit into Aldon.


This thread ...


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