Can you have multiple CMDB

[Brian Lancaster]

We have a requirement where we will be getting our CMDB from out customer will all the Services they order from us.   As part of this we are not allowed to modify the CMDB data.   Is there a way to have a second CMDB that we can use to be able to integrate CIs from other vendors that help support our overall customer?

[Dave Smith1]

The ITIL guidance says that there can be multiple CMDBs.

Your challenge should really be: who has ownership of each one, what does each contain and will there be overlaps/relationships between them?

We have a requirement where we will be getting our CMDB from out customer will all the Services they order from us. 

Do you maintain any inventory of services purchased from you?   It sounds like you're asking them what they've brought, not what you know you've sold.

As part of this we are not allowed to modify the CMDB data. 

Do you need to modify it, or just read it?   In theory, most support staff only need to look up information in a CMDB, rather than amend it.

Is there a way to have a second CMDB that we can use to be able to integrate CIs from other vendors that help support our overall customer?

Why are you integrating information from other vendors.. and they aren't?   Really.. whom does this CMDB serve?

[Brian Lancaster]

They are giving us what they bought.   I'm not worried about who owns each one as I already know that.   I cannot find any documentation on how to create a second or 3rd CMDB.

[Dave Smith1]

I cannot find any documentation on how to create a second or 3rd CMDB.

Okay.. I think the problem is getting clearer: are you prevented from amending the existing CMDB table structures (you can't extend one of their tables) or is it simply data in the CMDB you can't change?

Recall that the CMDB in SN isn't just one table, it's a series of tables. Although they may manifest themselves as multiple tables in one CMDB, in reality it's possible to lock down specific table accessibility to make it appear as several different segmented databases.

[kristenankeny]

What about using a group field to determine who "owns" that particular CI and using that in ACLs to control which you can edit? This way, you wouldn't be able to edit their records, but you could edit your own records.