Table Part Partitioning

[Sashi K1]

Hi

From Jakarta we are observing new Table Part Partitioning on most of out of the box tables that includes CMDB. Now we see table fields which were inherited from CMDB are now part of individual tables. Eg. Name field from CMDB were showing pre-jakarta as 'Name' field belong to CMDB from a cmdb_ci_server table. Now with Jakarta, every 'name' column on child tables show that belong to same table. I know its Service Users wouldn't be impacted by this TPP, however would like to make sure we have right preparations prior upgrading.

Now question(s);

1. What is the core benefit of TPP? Is that performance improvements?

2. Why CMDB or most of tables partitioned from Jakarta?

3. In what way it impacts Discovery or Service Mapping?

4. Do have to know anything? Would that impacts any of our scripts related to 'inherited' functionality?

5. TPP improves platform upgrade? if yes how?

Could anyone from ServiceNow platform or CMDB provide more information on TPP? Also I greatly suggest to create a Blog Post that explains. Huge benefit making your users to gain design knowledge.

Thank you

[Sashi K1]

Hi Soren

This discussed is not endorsed by ServiceNow yet, however you find useful information to understand TPP.

However you would find community leader pradeepksharma part of discussion. Pardeep any documentation on TPP?

[Pradeep Sharma · Accepted solution]

Hello Sashikanth,

Below are some helpful links on this topic.

Table flattening  

andrew.venables shared some excellent information on this Jakarta CMDB Changes

I hope this helps