Should you add columns to the cmdb_ci table?

[davidglover]

I've got a business need to track some legacy information for various CI's.     In total, there will be 8 new attributes that run across 32 different CI classes.  

Question to the community is, should I:

A) Add the columns to the cmdb_ci table so that the attributes are available in all the extended tables (seems risky since this is a "core" table)

- or -

B) Create a custom table to store the 8 new attributes and reference back to the cmdb_ci table.

Anyone else run into this situation and safely extended the cmdb_ci AND still been okay with the decision years later?

Thanks!

David Glover

[Michael Fry1]

Go with A. You're just adding some fields to the base table so the fields are available in all extended tables.

[davidglover]

Thanks Mike!