If you want to know how much space your OperationsManger database is using you could run a SQL Report. Because it is a feature from SQL Server 2008 R2 it’s easily overseen I just want to show an example.
Open SQL Server Management Studio navigate to Operations Manager database and make a right mouse click. Click “Reports/Standard Reports/Disk Usage”…
After a few seconds a pie chart will be shown. On top you see the total size of the database including log file and also each file size of the data and log file. Usually a database should have “Unallocated” (green) space available.
My left pie just shows that “Data”, “Unused” and “Index” uses the entire space. This means my database is full. Since OperationsManager database does not autogrow it just stays this way.
The side effects are several critical alerts and the eventlog will show e.g. errors like event id 10801…
To resolve this, just resize your database. First calculate how much space for your OperationsManager database you need by using the Sizing Helper Tool . Then go into the database properties and set the appropriate settings. SCOM 2012 configures by default the transaction log half the size of the database log, keep this in mind. Click o.k. and SQL Server will resize the database. You don’t need to reboot your servers nor anything else.
Next run the SQL Server Report again and finally you get “Unallocated” space…
No comments:
Post a Comment