RE: Aldon & Index Advisor Indexes

["Paul Nelson" <nelsonp@xxxxxxxxxxxxx>]

I don't know. I've never tried it. Given that Aldon can "retrieve" the
source code for a table/index when it is loaded to the release, I'm not sure
what would happen if it tried to deal with an index advisor object. 

I don't use SQL, but is a new index advisor object created whenever an index
is recreated? 

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, December 04, 2012 8:23 AM
To: Midrange Systems Technical Discussion
Subject: Re: Aldon & Index Advisor Indexes

Why would you not just add the index as a pseudo-source object?

Charles


On Tue, Dec 4, 2012 at 9:14 AM, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:

> I would create the index advisor source into a *SRCMBR object and tie it
to
> the index as a dependent object. That way, whenever you need to modify the
> index, you can check them both out, modify the index, and then paste the
> new
> source into the *SRCMBR.
>
> That should keep the loop closed in terms of audit tracking and whatever
> change control standards you have.
>
> Paul Nelson
> Cell 708-670-6978
> Office 512-392-2577
> nelsonp@xxxxxxxxxxxxx
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sam_L
> Sent: Monday, December 03, 2012 8:32 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Aldon & Index Advisor Indexes
>
> 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.
>
> Sam
> --
> 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.