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

There may be a situation where the SQL Logs take up a lot of space when the Webgility Desktop program is installed on a local server and is handled by an internal or external IT team for the user (When Webgility Desktop is not placed on a hosted environment).

The SQL Logs occur because of SQL's excessive "error" recording activity. This results in the creation of unnecessary error logs that are not being used.

The 'DBUtility' program from Webgility can assist in resolving this problem and keeping the C: drive free of any unnecessary logs.

SQL is always installed on the C:\ drive of your server computer.

To check the ‘Logs’ folder of SQL, we need to access the below path:

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

OR

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

Reviewing the SQL installation and the ‘Logs’ folder, we can see the size of the 'ERRORLOG' files on this page.

The files' sizes can be measured in gigabytes. You may remove the logs if they are large and using needed disk space.

1). Once the issue has been located, the first step is to disable Webgility's automation and end the Webgility Desktop application from running on all machines, assuming it has been set up and is now running on the additional systems.

Below is a reference article which gives an overview of the scheduler.

https://helpcenter.webgility.com/en/articles/6247434-overview-of-the-scheduler-in-webgility-desktop

The scheduler icon becomes ‘Grey’ in color indicating that the automation is turned OFF.

2). Next, please click on the ‘Windows’ icon on the bottom left-hand side of the screen, and type services to access the Services menu.

3). In the Services menu, you will need to select the active database service SQL Server (Database Name)> then Right-click on the name and select the Stop button.

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). Now, to delete the ERRORLOG files, please access C:\Program Files\Microsoft SQL Server\MSSQL13.UNIFY\MSSQL\Log> Select the ERRORLOG files> Right-Click> Delete.

5). Once these log files are deleted, please access the Services menu once again Right-Click on the service SQL Server (Database Name) which was stopped earlier, and click on Start.

6). Close the Services window and please access C:\Webgility\UnifyEnterprise and double click on the file named UnifyDBUtility to run the file.

7). After the Utility file has finished running, you can restart the Webgility application and scheduler. From now on, SQL will be prevented from making excessive logs.

If you have any issues after performing the above steps, please send an email to support@webgility.com You may also navigate to webgility.com to chat with our support team or use the chat option from within the Webgility application itself!