How can i minimize NCM_ConfigParsedArchive table Size?

sayalirevalkar

Hi All,

Need your support to minimize the table size for NCM_ConfigParsedArchive table.

Also, let me know what data this table contains?

When i am deleting old configs, the NCM_ConfigArchive table size is decreasing, but NCM_ConfigParsedArchive is the same.

As this table size is huge as per OEM, i want to decrease its size.

Thanks..!!

GoldTipu

Firstly i would recommend you to upgrade to NCM 7.8 if currently the table size is very large as this is known issue with NCM 7.7 release.
If the any customer uses 7.7 then I recommend to upgrade it because on 7.7 there was a bug about not cleaning orphaned data in DB maintenance job.It’s a part of db cleanup because when a config is deleted then also related parsed data is deleted.

This table contains parsed, common data from configs. It’s used not only by NCM ACL but almost every new feature which we make. Also we provide some data for NPM from that.

I really don’t recommend to clear that table manually.

Now if you are already on NCM 7.8 please review below.

In NCM we don't only store raw, text config but also we parse it and keep model in the database.

That data is not only needed to view on UI but also needed by our algorithms like the Shadow Rule Detection or later writing configuration into devices. Sometimes those 'few lines' contains a lot of valuable data which NCM has to parse and store.

I recommend to review and configure purge configs and DB maintenance NCM jobs.

Those jobs remove old and odd data. This is the only way to solve this issue.

Also if you were using the ASA Rules in NCM you should expect this growth .

If you still see dbo.NCM_ConfigParsedArchive table is too large review your DB Maintenance Job logs

C:\ProgramData\SolarWinds\Logs\Orion\swdebugMaintenance.log

check if there is any Error there ?

Open support ticket with Solarwinds see post below.

Tips and Tricks on opening a Support Ticket with SolarWinds - SolarWinds Worldwide, LLC. Help and Support