I want to know is there any data limit for cmdb

[kiran kumar m1]

while we do e-bonding  lots of records get created from different instances , I want to know is there any data limit for cmdb , such that it can handle this many records? any limit?

[Sohail Khilji]

Hi @kiran kumar m1 ,

For CMDB there is not limits when it comes to data size or tables. It provides hefty space for your multiple sources to update the data in cmdb. Only thing you have to do is to efficiently manage and maintain a clean and healthy cmdb with propery sanity/ cleanup checks... 

if you have huge data, then check with your account manager to see what capacity is alloted to you beyond your contract..

i hope this helps...

[Tai Vu]

Hi @kiran kumar m1 

it seems there's no technical limitation for the number of records per table. You can have a look to below threads for contractual limitation.

What are data storage limits for an instance

Maximum number of records the table can manage

Cheers,

Tai Vu

[Ashok Sasidhara]

There should not be any data limits specific to the CMDB. But it is definitely not recommended to populate too much of data in the CMDB due to the following reasons:

1. Increased amount of data gives rise to possibility of performance issues while opening any tables which contain a very huge volume of records (this is valid for non-CMDB tables also).

2. It is recommended that the CMDB only holds data which is required for some business objective. i.e. We should not populate data just because the data is available to populate from any source. So consider only the tables and attributes which are required for various use cases like incident management, change management, event monitoring, asset management etc. 

3. Presence of huge volumes of data will make it more difficult to monitor and manage the data. It is important to monitor the CMDB data quality on an ongoing basis and take actions to remediate data quality issues.

So please make sure that only the required CI classes and attributes are populated which are important for the organization's business objectives. Also there should be data retention and archival policies in place. i.e. Retired CIs should be archived after a certain pre-defined period (E.g. 2 years) and the archived CIs should be deleted after a certain pre-defined period (E.g. 5 years). This is very important to ensure that old and irrelevant data are not unnecessarily kept in the CMDB.