Custom table best practise

[KeerthanM]

I have requirement to create custom table, due to the licensing impact we are thinking to extend the cmdb table and create new table. Is this a correct approach, can you please help with the best practise.

[Ankur Bawiskar]

@KeerthanM 

not good practice to extend cmdb_ci

Please follow standard practice to use custom table and discuss with your customer about the licensing

If your customer is paying for custom tables then why not use that

Financial Implication of Extending Tables 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar]

@KeerthanM 

Hope you are doing good.

Did my reply answer your question?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Dr Atul G- LNG]

Hi @KeerthanM 

Creating a new customiztion table is a significant customization and will increase technical debt, so it should be avoided. Consider whether the purpose of this new table can be fulfilled using out-of-the-box (OOB) tables only. Instead of extending the parent table, it’s better to explore child table extensions if needed.

[Aswin S]

Hi @KeerthanM 

Extending a CMDB table should only be done if the data represents a true Configuration Item (CI). Using CMDB extensions solely to avoid licensing impact is not a best practice and can cause issues with CMDB integrity and future upgrades.

If the data is not a CI, create a custom table outside the CMDB. If it is a CI, extend the appropriate CMDB class (cmdb_ci or its child). Always align with CMDB best practices before proceeding.

Regards,

Aswin