---
title: "Local database space issues | Lansweeper Classic"
slug: "local-database-space-issues-when-linked-with-cloud"
description: "Resolve local database space issues that affect a Lansweeper Classic installation linked to Lansweeper Platform. Reduce your database size and prevent sync errors."
updated: 2026-06-25T19:52:23Z
published: 2026-06-25T19:52:23Z
canonical: "docs.lansweeper.com/local-database-space-issues-when-linked-with-cloud"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Local database space issues when linked with Lansweeper Platform

Microsoft limits SQL LocalDB and SQL Server Express databases to 10 GB. If your Lansweeper Classic database approaches that limit, keep an eye on its size to prevent problems.

When the database is full or nearly full, your Lansweeper server can stop working correctly, which leads to incomplete or out-of-date data. If your installation is linked to Lansweeper Platform, that same incomplete data syncs to the Platform, or the sync stops altogether. If the database hits its size limit during a Lansweeper update, the update can also fail.

When the database reaches 90% of the size limit, a notification appears in the web console. Only users with the **Access Configuration** permission see it. You can dismiss the notification, and it clears automatically once the size issue is resolved.

You can find the current size of your database in the Scanning Status widget or the sync status section of the **Configuration** > **Link with Cloud site** menu.

## Reduce your database size

1. Identify which database server hosts your Lansweeper database using the ConfigEditor tool. See [Identify which database server Lansweeper is using](/classic/docs/identify-which-database-server-lansweeper-is-using).
2. In **Windows Services** on all your scanning servers, stop the **Lansweeper Server** service and the web server service. This logs everyone out of the console. The web server service is either IIS Express or World Wide Web Publishing Service (IIS).
3. Run the DatabaseMaintenance tool on your Lansweeper server, at `Program Files (x86)\Lansweeper\Tools\DatabaseMaintenance.exe`.
4. Select **Truncate logs**, then **Shrink**, then **Compact**. Each operation can take a while.

This clears the `tblNtlog` and `tblNtlogMessage` tables, deleting all Windows event log data from your database. Event log data usually takes up the most space. You can still scan new events afterward.
5. Restart the **Lansweeper Server** service and the web server service in **Windows Services**, then wait a few minutes for the automated cleanup to finish.

              Move to full SQL Server for more space

              

If you keep hitting the database size limit, move your Lansweeper database to a licensed SQL Server edition, which has no fixed size limit. See [Move your database from SQL LocalDB to SQL Server](/classic/docs/move-your-database-from-sql-localdb-to-sql-server), or if you're already on SQL Server Express, [Move your SQL Server database to a different server or instance](/classic/docs/move-your-sql-server-database-to-a-different-server-or-sql-server-instance).

For more on managing database size, see [Perform automated database cleanups](/classic/docs/perform-automated-database-cleanups).