App Control: How to Shrink the Das Database After Filenames/Pathnames Offline Pruning

[#1]

Environment

• App Control Server: All Supported Versions
• Microsoft SQL Server: All Supported Versions

Objective

How to shrink the DAS Database to free up space after running the offline pruning script

Resolution

Warning: Shrinking the Database files could take significant time depending on DB size and the SQL Server performance

1. Take a full backup of the DAS database.
2. Stop the App Control Server and App Control Reporter services
3. In SQL Server Management Studio execute the following query to locate any remaining SQL tasks connected to the das database that should be stopped:

   sp_who2

4. Expand Databases > right click das > Tasks > Shrink > Files > for each Filegroup (as needed):

   Note: Only use the "Release unused space" option should be used.

   • PRIMARY
   • SECONDARY
   • ABINST
   • ABTEMP
5. Click OK
6. Once the shrink completes check that the initial database file sizes are set appropriately:

   Note: The Initial Size (MB) is updated automatically by SQL Server. Even if the Initial Size is set too low (e.g. 1MB) it will be automatically increased to prevent issues.

   • Right click the DAS database > Reports > Standard Reports > Disk Usage > Expand "Disk Space Used by Data Files" table > note the "Space Used" value
   • Right click the DAS database > Properties > Files > Check the "Initial Size (MB)" value for every file matches the "Space Used" value from the report
   • If the "Initial Size (MB)" is set too high > update it downwards, so that it matches the "Space Used" value from the report
7. Start the App Control Server and App Control Reporter services

Additional Notes

• It is recommended to first verify the appropriate steps have been taken to free space in the database.
• Additional information on shrinking Microsoft SQL Server databases is available here.

Related Content

App Control: How to Free Space in the DAS Database
Shrink a database - SQL Server