SCOM 2016 should have maintenance to clear out unused space with SQL 2016
SCOM 2016 has a issue that becomes evident over enough time where unused space on Performance and Event Tables grows and eats up the space in the SCOM SQL Database to the point that SCOM can not perform its nightly maintenance and then a Group job across the 62 partitions needs ran to clear out this unused space. The maintenance to clear out this space should already be included to accommodate the issue where SQL 2016 changed its bulk insert.
Alistair Ross [MSFT] commented
This issue can be mitigated with simple SQL Server Maintenance task.