Question

2
Replies
79
Views
JohnPaulRaja,C Member since 2011 246 posts
Cognizant
Posted: 1 year ago
Last activity: 1 year 3 months ago
Closed

Work table split-up

Application have 5 different work objects types, all the work object types are sharing the same work table.

Though we have required indexes on the work table, performance is poor, we are planning to split the work table, have separate work table for each work object type

Class structure before split up

Org-Div-Unit-work - is Class group and point to PC_WORK and HISTORY_PC_WORK

-Org-Div-Unit-work- ob1 -belongs to class group

-Org-Div-Unit-work- ob2 -belongs to class group

-Org-Div-Unit-work- ob3 -belongs to class group

-Org-Div-Unit-work- ob4 -belongs to class group

-Org-Div-Unit-work- ob5 -belongs to class group

Class structure after split up

Org-Div-Unit-work - is Class group and point to PC_WORK and HISTORY_PC_WORK

-Org-Div-Unit-work- ob1 - is Class group and point to PC_WORK_1 and HISTORY_PC_WORK_1

-Org-Div-Unit-work- ob2 - is Class group and point to PC_WORK_2 and HISTORY_PC_WORK_2

-Org-Div-Unit-work- ob3 - is Class group and point to PC_WORK_3 and HISTORY_PC_WORK_3

-Org-Div-Unit-work- ob4 - is Class group and point to PC_WORK_4 and HISTORY_PC_WORK_4

-Org-Div-Unit-work- ob5 - is Class group and point to PC_WORK_5 and HISTORY_PC_WORK_5

After changing the class structure, each class group creates a separate HISTORY table.

Questions

1. How to handle History table data, existing data holds class group is ‘Org-Div-Unit-work’, but new class groups are Org-Div-Unit-work- ob1, ob2, ob3, ob4, ob5

2. Do we have any other easy way to do table split up and handle existing data?

Low-Code App Development Case Management Data Integration
Moderation Team has archived post
Share this page LinkedIn