I'm currently having a performance problem related to SCOM that I'm trying to resolve.
Procedure sp_spaceused appears to be consuming a lot of tempdb space in my SQL 2000 instance, to the point that tempdb free space is almost gone.
This seems to be occurring when the sp_spaceused process is blocked by another server process.
I am certain that stored procedure sp_spaceused is being executed by a SCOM rule/monitor that ships with the SQL Server management packs: the user is NT Authority/System, which is the SCOM user.
I think sp_spaceused is being called from the DB Space Free monitors.
To confirm, I looked through the SQL2000 Monitoring management pack (in XML) and could not find any occurrence of sp_spaceused.
What am I missing?
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]