We recently migrated our SCOM database onto a new SQL 2016 instance, and since the migration the DB keeps filling, despite the fact that we aren’t seeing a higher alert volume than when it was on the previous 2012 instance. Is there some missing setting required, or is SQL 2016 not supported?
1 Like
I had that issue after installing a new SQL management pack a while ago.
I used som scripts from “running checks” here to find the issue:
http://www.bictt.com/blogs/bictt.php/2014/10/10/case-of-the-fast-growing
In my case I found that the issue was a store procedure by the name “sql visualisation”
It could be something similiar in your case.
Hi,
did you already checked this?
https://blogs.technet.microsoft.com/germanageability/2017/07/07/possible-increased-unused-disk-space-when-running-scom-2016-on-sql2016/
3 Likes
Could you run a report to see what table is growing?
Try using Kevin Holman’s SQl querries, to spot what is using up all the space.
https://blogs.technet.microsoft.com/kevinholman/2016/11/11/scom-sql-queries/
My experience is that event collection is sometimes running wild 