Best practice for adding fields to a table from another table

[AM24]

Hello,

I want to add fields to a specific OOTB table. Now adding new fields to that table takes a very long time for releases. Therefore, it has been suggested using a separate table and have those fields appear in the original table. For the new table, is it better to extend the table and add it there? Or would it be better to create an entirely new non-extended table with a reference to the original table, and add fields there? I have seen it done both ways, so I was just wondering what would be best practice. Thank you.

[Dipu Joy · Accepted solution]

Extending an existing table or Creating new fields on an existing table depends on your use case, and there are no Best practices around it. If it is a new table, this can be calculated against your custom_table, which can attract $ depending on your contract. Creating a new field on task/CMDB* can take longer when done directly on PROD, which has a lot of data, and sometimes the UI can time out ( 300s). The recommendation is to capture it in the SUBPROD on an update set so that creation is a backend transaction without the timeout. These KBs explain the details of creating, updating, and deleting fields.

Best Practice of Column/Field Creation (and Deletion)

Creating or altering a field on a large table from the UI can be canceled by "UI Transactions" Quota...