Guidance on good practice cleaning data from sys_update_version

[Mike Veitch]

Is there any recommendation on retaining record in sys_update_version. Its one of our biggest tables obviously and wondering if you’ve come across anyone having done anything with clean-ups on it. Obviously you lose the ‘restore to version’ if you remove but wondering how far back this really needs to go

[Community Alums]

Hi @Mike Veitch ,

You can refer to these threads :

https://community.servicenow.com/community?id=community_question&sys_id=70c4c3d5db596300f21f5583ca96...

https://community.servicenow.com/community?id=community_question&sys_id=fc154b131bd28d1056b699b8bd4b...

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[User192098]

This is more about the practice of retention of records specifically in sys_update_version and not how to cleanup

[Artur Debiec Ce]

I am having the same challenge, obviously we want to keep these records for a while...but for how long ?

Also, I do not think data retention policies in the Organization would help here, as this is more about what was configured/developer rathe than data.

I would personally look at number of records plus their storage consumption. Then depending on your budget (for storage) make a decision.

[Tim Grindlay]

The sys_update_version table was also the biggest table on our instance by a mile. Turns out the em_connector_instance table was responsible for 93% of its size. These are for event management connectors like SCOM and Solarwinds. Resolution is to raise a case with Now Support.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0998845