Local database space issues when linked with Cloud

Cloud is a feature introduced in Lansweeper 9.0. If you are using an older Lansweeper release, you will need to update by following the instructions in this knowledge base article.

As both SQL LocalDB and SQL Server Express databases are limited in capacity by Microsoft to 10 GB it is important to keep an eye on the size of your Lansweeper database, to prevent it from reaching its maximum size. When the database is full or almost full, your Lansweeper server might stop functioning as it should, resulting in incomplete or out of date data. If your on-prem installation is linked to Cloud this may result in this same incomplete or out of date data being synced to Cloud, or your sync stopping altogether. Additionally, if your database reaches its size limit during a Lansweeper update, the update may fail.

When the database reaches the size limit of 90% a notification will be shown in the on-prem web console. This notification will be shown to users that have the Access Configuration permission only. The notification can be dismissed, and it will automatically disappear if the database size issue is resolved. This article explains how you can quickly reduce your database size to avoid any impact on your sync with Cloud.

 

The size of your database is listed in the Scanning Status widget or sync status section of the Configuration\Link With Cloud Site menu.

How to quickly reduce your database size

Step 1: Determine your database server

You can determine which database server is hosting your Lansweeper database by using the ConfigEditor tool. You can follow the instructions in this knowledge base article.

Step 2: Stop the Lanweeper service

Stop the Lansweeper Server service in Windows Services on all of your scanning servers.

stopping the Lansweeper service

Step 3: Stop your web server service

Stop your web server service in Windows Services. Keep in mind that this will log everyone out of the console. Your webserver service is either IIS Express or World Wide Web Publishing Service (IIS).
stopping the web server service

Step 4: Run DatabasMaintenance.exe

Run the following tool on your Lansweeper server: Program Files (x86)\Lansweeper\Tools\DatabaseMaintenance.exe
running the Lansweeper Database Maintenance tool

Step 5: Truncate logs, Shrink and Compact

Hit the Truncate logs button, then Shrink and then Compact (if highlighted). Each operation may take a while to complete.

This step will clear the tblNtlog and tblNtlogMessage tables in your database, deleting all Windows event log information from your database. Event log data generally takes up the most space. You can still scan new events afterward.

Step 6: Start the web service

Restart the webserver service in Windows Services.

starting the web server service

Step 7: Start the Lansweeper service

Restart the Lansweeper service in Windows Services and wait a few minutes for the automated cleanup options to finish running.

starting the Lansweeper service

For further steps to manage your database size, you can refer to this article.

If you would keep running against the database size limit, we recommend moving your Lansweeper database to a licensed SQL Server edition that has no fixed database size limit. To move your SQL LocalDB database to SQL Server, you can follow the steps in this article. If you are already using SQL Server Express, you can follow these steps to move to another SQL Server instance.

Related Articles

Get Started Right Away

Try Lansweeper for Free