Want to add index on wo_mstr

[Chris Kelleher]

Hi

Since we are going to handle more than 800 W/O a day, we would like to
group W/O transactions by using the wo_so_job field (for instance, to close
several w/o, the user calls for a wo_so_job number and a specific program
closes all the w/o which wo_so_job have the same values).

But since this field is not indexed, I fear some response time issues.

So here is my questions:
-what is the impact of adding an index on this field (wo_so_job of wo_mstr) ?
-Do I have to recompile all programs that use wo_mstr ?
-how does it impact the QAD index utility tools ?

Thanks for your answers
Toan Nguyen
_______________________________
Viet-Toan Nguyen
Schlumberger Test & Transactions
SIBS - Project Manager Tours MFG/Pro
Tel: +33 2.47.74.87.37 (Tours)
Tel: +33 1.47.46.62.23 (Montrouge)
toan_nguyen@montrouge.tt.slb.com

 

[Chris Kelleher]

Viet-Toan,

Since no one has responded to this yet, let me toss in a thought or two.

First off, realize that by modifying the schema in MFG/PRO (and adding an
index does this), you are customizing the software and will never be able
to simply accept a patch or upgrade from QAD and apply it. You will need
to recompile everything that you receive, or at least verify that it
doesn't need to be recompiled.

If you're creating your own program to do this multiple work-order close
routine, then I'd suggest that you add a table in a side database which has
the work order information that you're looking for. Populate it with a
create trigger (on create of wo_mstr) and remove it with a delete trigger
(on delete of wo_mstr) and use that side table in your delete routine.

Of course, before you go through all that trouble, I'd see just what kind
of performance you will get. There may not be enough of an impact to
warrant additional effort in order to make all this work.

For the future, your MFG/PRO and Progress versions would make it a little
easier to answer your question.

Good luck.

Scott