Feb 22, 2019 - 12:33 AM
Feb 22, 2019 - 01:20 AM
Most designs I have seen don't make this clear.
There may be one database in your logical CMDB that is most heavily used (e.g. Service Desk ) but that does not mean it is the only database we will maintain. Common exceptions are financial information, real-time monitoring or HR specific information.
There are a couple of reasons you don't want one physical CMDB:
Cost of getting an all encompasing Tool
Resources needed to maintain it
Volume of data required
Complexity of interfaces to all of the potential sources
ITAM requires a lot of effort to collect, clean and normalise data before it is useful. This is better done outside of the CMDB with only the important information transferred to the final database.
That's not to say you can;t have a single view of the data but you must assume there will be multiple database the data will be maintained and refreshed to produce this view
Feb 22, 2019 - 07:06 AM
I concur with Piaras; a single view doesn't infer a single repository!
The various technologies (MS, MAC, Citrix, IBM, Vmware....) and various topologies ( isolated LANS, DMZ, Protected Server Farms.. and laptops on Dining room tables) effectively demands any 'SAM' endeavour to accept & absorb heterogeneous inventory/purchase/user data.
Though a CMDB *could* be considered an inventory source ( danger!), it should not considered the 'ultimate' inventory source for SAM 'views'.
At the end of the day, both SAM & CMDB need to consume raw inventory data. But if you create a 'chain of data transfer where Inventory=>CMDB=>SAM... you've created a IT version of 'Chinese Whispers/Telephone' where data interpretation could create dangerous artifacts.
Mar 05, 2019 - 07:53 AM
In _theory_, CMDB as The Only One source of accurate, complete, up-to-date and valid data makes sense. In therory, it might containt all the data requered for SAM and in theory, it is great resource for SAM.
But I have never seen this CMDB, which is the ultimate wish for every IT manager...
Also, you need to integrate some logic above this raw data (Snow, Flexera, Aspera, ...) and they will accept output from, lets say, SCCM. But from CMDB?