purge or delete or re-initilaise sbsmonitoring database (sbsmonitoring.mdf, sbsmonitoring.ldf)

Michael Green
Michael Green used Ask the Experts™
on
Hi,
I currently have the SBSMonitoring database using a huge amount of space on Small Business Server 2008 (sbs2008)

sbsmonitoring.mdf    994.2MB
sbsmonitoring.mdf    611.1MB

Is there an easy way to purge, delete or re-initialise this database to get the size down ?

Regards
Michael
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Hi:

In the SBS console, under Monitoring, run the setup wizard.  This will clear the history so you will not have comparisons in the reports, but it will lower the space consumed.

How big is your system partion?  1.5 GB is not "huge" for this database.
Michael GreenSenior IT Consultant / IT Project Manager

Author

Commented:
Where is 'Monitoring' located on the SBS2008 console ?
Sorry, keep getting the versions mixed....

You still are nowhere near any limits on these files.  If your system partition is lacking free space, either the partition is too small or there are other things using the space.

Here are two articles that explain it.  Note, Please read them both to the end.

http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx

and

http://www.thirdtier.net/2010/03/sbs-2008-monitoring-database-fills-to-capacity/
Learn SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Michael GreenSenior IT Consultant / IT Project Manager

Author

Commented:
The customer's C: drive is quite small - hence the issue.

I read all three articles - have seen this about updateSBSMonitoring.sql  before.

I ran updateSBSMonitoring.sql per the procedure.

It did NOT decrease the database size - it INCREASED IT !.  And the log file size TOO ! (to over a gig).

Is this the result you expected ?
Not what I expected and not sure what that is about, but you will be fighting this forever.  Probably better to increase the size of the system partition.

Also, "run as administrator" either wirdirstat or treesizepro to see what else is consuming space on that system.
Senior IT Consultant / IT Project Manager
Commented:
OK - it looks like it needed a shrink as well.  Database is now 120Mb.

Here is the batch file I developed that worked :


Rem script developed from :
Rem http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx

Rem Find and stop the SQL Server (SBSMONITORING) service.

NET STOP MSSQL$SBSMONITORING

MKDIR C:\TEMP
MKDIR C:\Temp\DataBackup

Rem backup all databases and log files in this directory
XCOPY /E /C /H /R /Y "C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data\*.*" C:\TEMP\Databackup

Rem Restart service
NET START MSSQL$SBSMONITORING

Rem Run downloaded SQL to EXECUTE [SBSMonitoring].[dbo].[CleanupDatabase] create indexes and statistics

Sqlcmd -S %computername%\SBSMonitoring -E  -i c:\Batch\updateSBSMonitoring.sql

sqlcmd -S %computername%\SBSMonitoring -E  -i c:\Batch\shrinkSBSMonitoring.sql

PAUSE
Michael GreenSenior IT Consultant / IT Project Manager

Author

Commented:
And yes - Windirstat is very useful.  But that is how I identified this size issue in the first place...:)
Michael GreenSenior IT Consultant / IT Project Manager

Author

Commented:
Solution required combining multiple steps/suggestions

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial