TPP (Table per Partition) Table Structure for CMDB in Jakarta upgrade

[Sanjeev Kumar1]

During the Jakarta upgrade, the CMDB table goes through a migration process that converts its hierarchy model from TPC, Table per Class, to TPP, Table per Partition.

I looked @ https://community.servicenow.com/community?id=community_blog&sys_id=64bc6a25dbd0dbc01dcaf3231f961916&view_source=searchResult 

It's good if someone provide information about it with some simple example.

[sergiu_panaite]

What kind of examples are you looking for? 

[Sanjeev Kumar1]

It will effect our reports if report is ruining on CMDB base table ? 

[sergiu_panaite]

Should not affect your reports!

[SwarnadeepNandy]

Hi,

As per my understanding, there is no change for the ServiceNow admins, but in the background Servicenow has changed their DB architechture.

In TPC (Table per Class) model, there was separate logical tables in the servicenow database. In jakarta they have incorporated table flatenning architechture. In TPP (Table Per Partition), all parent(cmdb) and children(cmdb_ci_hardware, cmdb_ci_computer etc.) are stored in a single logical table. New tables are getting created on demand basis which is known "partition". So if the single logical table is exceeding particular size limit a new partition will get created named as cmdb$par1, cmdb$par2 etc.

Note: This has no impact for the ServiceNow developers, its purely an internal DB architechture change.

Thanks & Regards,

Swarnadeep Nandy