Skip to content
  • There are no suggestions because the search field is empty.

How to Delete Increasing SQL Logs/Dump Files and Control Disk Space Usage, Preventing Them From Happening in the Future

This article helps Webgility Desktop users manage and prevent excessive SQL Server log file generation that can consume significant disk space. When using Webgility Desktop with a SQL Server instance, detailed error logging can result in the accumulation of large log or dump files. These files are often unnecessary and can lead to storage issues if not regularly maintained.

Overview:

SQL Server generates logs for system activities and errors. In environments where Webgility Desktop is hosted on local servers (typically managed by IT teams), these logs can grow rapidly. Over time, they may occupy several gigabytes of storage, leading to performance issues or space constraints.

Steps to Delete SQL Logs and Prevent Future Growth

How to identify if SQL Logs are consuming space?

SQL Server typically gets installed on the C: drive of the server/machine. To locate the SQL logs, navigate to one of the following folder paths:

C:\Program Files\Microsoft SQL Server\MSSQLXX.WEBGILITY\MSSQL\Log

OR

C:\Program Files (x86)\Microsoft SQL Server\MSSQLXX.WEBGILITY\MSSQL\Log

NOTE: The 'XX' in the MSSQLXX will be the version of the SQL Server that your Webgility Desktop hosting the database on.

Within the Logs folder, locate files named ERRORLOG. These files may consume significant space.

Steps to follow: 

Stop Webgility Scheduler (Automation)

Before proceeding, disable Webgility Scheduler (Automation) by stopping and then exiting scheduler properly.

Follow the steps in this helpful article on How to start Scheduler

Once disabled, the scheduler icon will turn grey.

 Stop the SQL Server Service (for Webgility Desktop Database Instance)

  1. Click the Windows Start icon and search for Services.

  2. Open the Services menu.

  3. Locate and right-click on the SQL Server (Webgility Desktop Database Instance Name) service.

  4. Select Stop.

Verify Database Name (Optional):

In case if you do not know Webgility Desktop Database instance name then you can verify it in the ApiConfig file available under the location C:\Webgility\UnifyEnterprise\XML
 

Open the APIConfig file and verify the Data Source (your database name).

Delete SQL Logs

After stopping the SQL Server Service for Webgility Desktop database then navigate to the following folder path: 

C:\Program Files\Microsoft SQL Server\MSSQLXX.UNIFY\MSSQL\Log

Locate and delete the ERRORLOG files.

Restart SQL Server Service for Webgility Desktop database

Return to the Services menu. Right-click the SQL Server (Database Name) service and select Start.

Run Webgility DB Utility

To prevent this from happening in the future, you will need to run DBUtility. This will ensure that SQL does not continue generating excessive logs.

To run the DBUtility file, navigate to the folder path C:\Webgility\UnifyEnterprise look for a file with the name "UnifyDBUtility" and run it. It may ask you to take a latest backup of Webgility Desktop so allow the same and then let the process complete.


Restart Webgility Desktop and Scheduler

After deleting the SQL logs and running the UnifyDBUtility:

  1. Login back into Webgility Desktop.

  2. Restart the scheduler.