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

How to Clear Old Logs (SQL, Error, Shipping) and Save Disk Space

This article helps Webgility Desktop users in safely deleting SQL log files, optimize the database, and configure settings to reduce unnecessary log generation, thereby enhancing overall performance of Webgility Desktop.

Running low on disk space or experiencing slowness in Webgility? SQL logs, error logs, and shipping logs can accumulate over time, consuming gigabytes of drive space and impacting performance. Learn how to safely delete these log files, optimize your database, and stop unnecessary logs from being created in the future.

  • Press Windows + R, type services.msc, and hit Enter to open the Services window.

  • Scroll to find SQL Server (YourInstanceName) — commonly listed as SQL Server (WEBGILITY) or SQL Server (UNIFY).

  • Right-click on the service and select Stop.

📌 To verify the correct instance name:

  • Navigate to: C:\Webgility\UnifyEnterprise\XML\APIConfig.xml

  • Open the file and locate the <Data Source> entry — this reveals your SQL instance name.

Why This Happens

Webgility Desktop runs on a SQL Server database and writes error or event logs to your local drive. If these logs are not cleared regularly, they can cause:

  • Rapid storage bloat

  • Slower software performance

  • System instability

This is particularly common on in-house setups where maintenance is not automated.

🧹 How to Delete SQL Logs and Prevent Excessive Growth

1. Locate the SQL Log Folder

Navigate to one of the following folders (based on your SQL version):

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

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

🔍 Look for files named ERRORLOG—these are the logs consuming disk space.

2. Turn Off Webgility Automation

  • Close the Webgility Scheduler to pause all background tasks.

  • The Scheduler icon in the system tray should turn gray once disabled.

3. Stop SQL Server Service

  • Press Windows + R, type services.msc, and hit Enter to open the Services window.

  • Scroll to find SQL Server (YourInstanceName) — commonly listed as SQL Server (WEBGILITY) or SQL Server (UNIFY).

  • Right-click on the service and select Stop.

📌 To verify the correct instance name:

  • Navigate to: C:\Webgility\UnifyEnterprise\XML\APIConfig.xml

  • Open the file and locate the <Data Source> entry — this reveals your SQL instance name.

4. Delete SQL Log Files

  • Return to the SQL log directory.

  • Select and delete all files named ERRORLOG or with .txt extensions.
    These files are safe to remove once the SQL service is stopped.

5. Restart SQL Server Service

  • Go back to the Services window.

  • Right-click the SQL Server service and select Start.

6. Run Webgility DB Utility

  • Navigate to: C:\Webgility\UnifyEnterprise

  • Right-click UnifyDBUtility.exe and select Run as Administrator.

  • This tool cleans and optimizes the SQL database for better performance.

Note: Running DBUtility helps shrink the Webgility database size, improving overall system efficiency.

7. Restart Webgility and Scheduler

  • Launch Webgility Desktop.

  • Re-enable the Scheduler from the system tray.

🧼 How to Delete Error Logs and Shipping Logs

1. Enable or Disable Logging (Optional)

  • Open: C:\Webgility\UnifyEnterprise\XML\apiConfig.xml using Notepad.

  • To enable logs, set <Logger>True</Logger>

  • To disable logs, set <Logger>False</Logger>

  • Save the file and restart Webgility.

📌 Shipping logs are only created if shipping processors are connected in Webgility.

2. Delete Error Logs

  • Navigate to: C:\Webgility\UnifyEnterprise\Errorlog

  • Delete all files inside this folder.

3. Delete Shipping Logs

  • Navigate to: C:\Webgility\UnifyEnterprise\ShippingLog

  • Delete all files inside this folder.

🔁 Maintenance Tip

Repeat this clean-up process every 30–60 days, depending on system usage, to avoid performance issues and disk space warnings.