How to Delete Increasing SQL Logs/Dump Files and Control Disk Space Usage, Preventing Them From Happening in the Future
Overview:
When using Webgility Desktop with an SQL Server instance, excessive SQL log generation can result in high disk space consumption. These logs often accumulate due to SQL's extensive error logging, creating unnecessary files. This guide will show you how to delete SQL logs/dump files, control disk space usage, and prevent this from happening in the future.
Why This Happens:
SQL Server generates logs for errors and system activities. In some cases, particularly when Webgility Desktop is hosted on local servers managed by IT teams (instead of a hosted environment), these logs can grow rapidly. They can take up several gigabytes of space, leading to performance issues.
Steps to Delete SQL Logs and Prevent Future Growth:
1. Identify the Issue:
SQL is typically installed on the C: drive of the server.
To view the logs, navigate to the following path on your server:
C:\Program Files\Microsoft SQL Server\MSSQL15.WEBGILITY\MSSQL\Log
OR
C:\Program Files (x86)\Microsoft SQL Server\MSSQL15.WEBGILITY\MSSQL\Log
In the Logs folder, you’ll find the ERRORLOG files. These logs can sometimes be large, taking up significant disk space.
2. Stop Webgility Automation:
Disable the Webgility automation by turning off the scheduler.
Refer to this article for more information on turning off automation: Overview of the Scheduler in Webgility Desktop.
When automation is off, the scheduler icon will turn grey.
3. Stop SQL Server Service:
Click the Windows icon on the bottom-left, type Services, and open the Services menu.
Locate and right-click the SQL Server (Database Name) service and select Stop.
Verify the source name:
Please access and open the APIConfig file, which is located in the C:WebgilityUnifyEnterpriseXML folder. In the 'Data Source' section, you will see the name of the database, example is shown in the screenshot below:
4. Delete SQL Logs:
Navigate to the SQL log folder:
C:\Program Files\Microsoft SQL Server\MSSQL13.UNIFY\MSSQL\LogSelect the ERRORLOG files and delete them.
5. Restart SQL Service:
Go back to the Services menu, right-click on the SQL Server (Database Name) service, and select Start to restart the service.
6. Run Webgility DB Utility:
Open the C:\Webgility\UnifyEnterprise folder and run the file named UnifyDBUtility. This utility will help ensure SQL does not continue generating excessive logs.
7. Restart Webgility Desktop and Scheduler:
After cleaning up the logs and running the utility, restart the Webgility Desktop application and turn the scheduler back on.
Still facing issues?