While monitoring the SharePoint health
analyzer, I came across this error - Database has large
amounts of unused space
Following databases have large amounts of space allocated on the
disk but not in use. This may be due to recent deletion of data form the
database, or because the database has been pre-grown to a larger size. This database
will take up a larger amount of space on the file system unless it is shrunk
down to a smaller size.
The database can be shrunk in size using the DBCC ShrinkDatabase
command or the Shrink Database wizard in SQL Server Management Studio.
There are some errors on which you really need to take an action
but this one you can safely ignore! – Yes, you heard it correct. This is not a
critical error and there is no harm in ignoring this error.
If
you really want to take an action then you can simply shrink the database. In
the above error, you will see the name of the database for which its failing so
take the action and you are done.
Resolution:
Two ways – Either by SQL way or Central Administration (CA) way
to remove this error from the Health Analyzer!
SQL way:
1. Login to the SQL management
studio
2. Right click on the
failing database
3. Shrink it.
CA way:
1) Open the Central
Administration
2) Click on the health
analyzer list
3) Click on the rule
which is showing this error
4) Click Repair
automatically option which is on the top ribbon -> Once you click on it then
wait for few mins i.e. give some time to execute that job properly
5) Now there is a time
“Reanalyze Now”
If
you have any queries / questions regarding the above mentioned information then
please let me know. I would be more than happy to help you as well as resolves
your issues, Thank you.
Note:
If you find a different solution, please report it as a comment to
this post. Be sure to double-verify it: undo your solution and verify that the
problem comes back, then redo it and verify that the problem goes away.
Product Applies To:
a) SharePoint Server
2010
b) SharePoint
Foundation 2010
Reference:
Not only can you safely ignore this error, assuming you are not out of disk space or have some other extenuating circumstance, it is best practice from a SQL viewpoint to NOT shrink the database. You may see some pros and cons, but IMHO, you should not shrink the database as part of a maintenance plan, and only do it if it's related to a one time issue, such as deleting a LARGE amount of data from the database or something similar.
ReplyDeleteRegards,
Dave Crosby
Thanks for the valuable feedback Dave! This would be very useful for all the SharePoint communities...
DeleteIn SQL Server check for transaction log and Database file size. May be need to shrink them...
ReplyDeleteyou shouldn't need to shrink logs and file in sql server, this is a dba work to implement the correct autogrowth settings, and the correct spacing for sp databases in the health monitor in central admin, you can use the "repair automaticaly" option for fix this issue
ReplyDeleteLinks to information: http://technet.microsoft.com/en-us/library/hh564121(v=office.15).aspx and http://www.microsoft.com/en-us/download/details.aspx?id=24282
ReplyDeleteIn SharePoint, these are the steps you could implement to be SharePoint experts. Also find best SharePoint 2013 Certification Training in your locality at StaygreenAcademy.com
ReplyDelete