Kbase P13480: Dynamics. Indexing rules recommendations for Dynamics
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/12/2003 |
|
Status: Unverified
GOAL:
Dynamics. Indexing rules recommendations for Dynamics
GOAL:
Dynamics Indexing Guidelines
FACT(s) (Environment):
Dynamics 1.1A
FACT(s) (Environment):
Dynamics 2.0A
FIX:
Dynamics Indexing Guidelines.
1. No table should be defined without index.
Not following this rule may lead to preformances problems.
2. Every table should have an unique identifier.
That unique identifier should be an unchanging sequence value that has no external meaning at all and should not be expected to change. All relationship between tables should be based on this unique identifier.
3. Always put an index on a Foreign Key field that involves only that field.
That way, relationship can always be determine efficiently.
4. Never use RECID or ROWID of a record to relate records.
RECIDs and ROWIDs are not preserved across DataBase dumps and reloads, and now with support for multiple storage areas, they are no longer unique across the DataBase.