Moving columns to extension tables
To improve performance and reduce database throughput,
several columns were moved from two frequently used tables, NJEntity and
NJAct, to one of the newly created extension tables.
Columns related to audit functionality have been moved from the
NJEntity table to the NJEntityXAudit table; columns related to default
addresses, phone numbers, and other communication methods have been moved
to either the EntityXDefAddr table or the EntityXDefTel table.
| Column | Extension table |
|---|---|
| sysCreateTime | NJEntityXAudit |
| sysCreateUserId | NJEntityXAudit |
| sysEditTime | NJEntityXAudit |
| sysEditUserId | NJEntityXAudit |
| createTime | NJEntityXAudit |
| createUserAlias | NJEntityXAudit |
| createAuthorAlias | NJEntityXAudit |
| editTime | NJEntityXAudit |
| editUserAlias | NJEntityXAudit |
| editAuthorAlias | NJEntityXAudit |
| defaultAddress | EntityXDefAddr |
| businessAddress | EntityXDefAddr |
| billToAddress | EntityXDefAddr |
| shipToAddress | EntityXDefAddr |
| mailToAddress | EntityXDefAddr |
| homeAddress | EntityXDefAddr |
| defaultTelcom | EntityXDefTel |
| workPhone | EntityXDefTel |
| homePhone | EntityXDefTel |
| mobilePhone | EntityXDefTel |
| faxPhone | EntityXDefTel |
| smsEmail | EntityXDefTel |
| EntityXDefTel |
In addition, several columns were moved from the NJAct table to the
newly created NJActXAudit extension table.
| Column | Extension table |
|---|---|
| sysCreateTime | NJActXAudit |
| sysCreateUserId | NJActXAudit |
| sysEditTime | NJActXAudit |
| sysEditUserId | NJActXAudit |
| createTime | NJActXAudit |
| createUserAlias | NJActXAudit |
| createAuthorAlias | NJActXAudit |
| editTime | NJActXAudit |
| editUserAlias | NJActXAudit |
| editAuthorAlias | NJActXAudit |
Warning:
The Main.upgrade script creates the new extension tables and moves the columns from existing tables to these new tables. Depending on your data, this script may take a long time to run.
NexJ Systems recommends that you test the Main.upgrade script with sample production data to estimate how long the upgrade will take with your production data.
Alternatively, you may also comment out these steps in the upgrade script and have a database administrator manually execute the changes described above.