Frequently Asked Questions
Frequently Asked Questions
Shrink size of SQL DB
Posted by Zachary Wick (M-Files) on 10 September 2019 05:07 PM

Version 1.0 | Last Updated 5 March 2019

1     Overview / Work Notes

If a vault becomes very large, it can become slow and hard to search for objects. To this end, you can use the one-time export from the Content Replication and Archiving section of the M-Files Admin with the "Destroy exported objects" option checked, to export and archive objects that are no longer needed on a day by day operation.

If you are using SQL Server, this will not cause the size of the SQL Server database to shrink. A SQL Server database will always remain the exact same size or grow larger unless the shrink database operation is performed upon it.

Normally, all maintenance operations should be handled by M-Files and from the M-Files Admin. For this particular case, we will need to perform this operation from the SQL Server Management Studio.

2     Solution / Workaround

  1. Take the vault offline for this operation.
  2. From SQL Server, run the shrink db operation. The below link has information on how to perform the shrink operation on the SQL database.

 https://docs.microsoft.com/en-us/sql/relational-databases/databases/shrink-a-database?view=sql-server-2017

(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.

Help Desk Software by Kayako case