New Indexes on JD existing tables

[erpteam]

I want to generate new indexes on JDE existing tables. I would like to know if it is feasible to do so and the impact it would have on existing JDE tables as well as JDE existing Applications. I would also like to know the impact when we have a upgrade in future.
Would anyone like to share their experience or offer solutions, please advise.

 

[ronnet]

I have created some new indexes on OneWorld with no further impact,
what I would suggest is that never delete a OneWorld Index.

I am planning on upgrading to XE but I am not worried about the
indexes issue, JDEdwards I am sure is not going to recreate tables
on the upgrade, but I still need to find out.

Regards




Ronnet Patino
OneWorld Developer
Noritex - Panama

 

[ow_consult]

Indeces on JDE tables are created in next number fashion. This means if a
JDE table has indeces numbered 1->5, your amendment to the table (creation
of new index) will number 6.

At upgrade time, JDE preserves your change.

If JDE has added additional indeces, (number 6), it simply renumbers yours
to 7.

This has no affect on applications/UBEs, as indeces are not used in the SQL
statement to the table, but are instead dynamically rebuilt each time.

Trust this helps,
OWConsult
JDE Product Certified Specialist

 

[belladandy_jr]

Further to Ronnet's comment, actually indexes are created for faster
searching, hence produce faster performance as well. but there are certain
constraint need to be considered when creating indexes e.g. create indexes
on frequently searched column like columns that are searched for ranges of
key values, or columns that are grouped together during aggregration. unused
indexes or too much indexes in a table will decrease its
searching/performace. my advise is to drop any unused custom indexes as it
require disk space & increase overhead and database that have high read
activity should have more indexes.

an upgrade will preserve new tables and custom indexed on jde tables, but
will replace column added or removed from existing jde tables. this includes
changing field length, field type, and decimal position.

Bell
OneWorld Developer
One World B7332,SP 9, AS/400 V4R4M0
Windows NT; Win2000+Citrix Metaframe 1.8a

----- Original Message -----
From: "ronnet" <[email protected]>
To: <[email protected]>
Sent: Saturday, April 07, 2001 11:12 PM
Subject: Re: New Indexes on JD existing tables


http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OWDEV&Numbe
r=8764

 

[Zoltan_Gyimesi]

Never make new unique indicies unless you include all fields of an original unique index.

If you are on AS400 box then maybe you should make some other consideration too. I am not experienced on this issue.

Zoltán
P.S.: Please, next time include your system configuration information too into your post. Thanks.

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)

 

[Bill_Feeney]

Zoltan,
What do you mean? Are you saying only to add columns to an existing index?

Thanks,

Bill Feeney
JDE Technical Developer
B733.2, SP 13.1, Unix, Oracle 8.1.6

 

[Zoltan_Gyimesi]

Re: RE: New Indexes on JD existing tables

Hi Bill,
I try to explain (you know, my Eglish ...)

1.) Never touch any existing original OneWorl index (do not add, remove columns, change the order of fields in it or the change the properties of it e.g. Unique or non-unique).

2.) Never create new custom indices with UNIQUE property for original OW tables, except in one case, when you:
* include all fields of an originally unique index of the table into your custom index without adding any other field (only the order of the fields should be be different).

I hope, it is clear this time.

Zoltán



B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)