→ Upcoming Keynote Event - Introducing Lansweeper's 2023 Spring Release: 'Duvel' - Learn More
on
11-25-2019
07:30 PM
- edited on
12-15-2022
11:33 AM
by
Nils
From Lansweeper 7.2 onward, SQL LocalDB is one of the available database server options for hosting your Lansweeper database. The LocalDB option is a custom variant of Microsoft SQL Server 2014 Express. It was introduced into Lansweeper as a replacement for the deprecated Microsoft SQL Compact database server.
This knowledge base article provides further information on what LocalDB is, why it was introduced, how to manage it and how to convert from or to this database server.
Lansweeper's LocalDB database server option is based on SQL Server 2014 Express. It has many of the same properties as SQL Server but also some notable differences.
SQL Server 2014 was used as the basis for Lansweeper's LocalDB implementation as it is compatible with a wide range of operating systems and architectures. Below is a comparison between Lansweeper's different database server options.
Database server | Packaged with Lansweeper | Max database size | Support for distributed Lansweeper components | Support for multiple scanning servers | Lansweeper support status |
---|---|---|---|---|---|
SQL Compact | ✔ | 4 GB | ✘ | ✘ | unsupported from March 2020 onward |
SQL LocalDB | ✔ | 10 GB | ✘ | ✘ | supported database server |
SQL Server | ✘ (manual install required prior to installing Lansweeper) |
|
✔ | ✔ | supported database server |
LocalDB was introduced primarily as a replacement for the deprecated Microsoft SQL Compact database server option. Both database servers come packaged with the Lansweeper installer and are therefore easy to use. However, SQL Compact was phased out by March 2020 for multiple reasons:
Lansweeper tools like DatabaseMaintenance.exe and ConfigEditor.exe can be used to perform certain operations on your LocalDB instance, as is the case for other database servers. For instance, you can change the LocalDB database password in the same way as you would change a SQL Server password.
In addition, you can connect to your LocalDB instance using SQL Server Management Studio (SSMS), though only locally from your Lansweeper server. The following users have access to your LocalDB instance by default:
Your SQL instance name under LocalDB is (localdb)\.\LSInstance
. Using this server name and one of the two user accounts listed above, you can access your Lansweeper database using SSMS.
You can convert a SQL Compact database to LocalDB. You can also convert a LocalDB database to SQL Server, if you require the added SQL Server functionality. It's theoretically possible to migrate from SQL Server 2014 or older to LocalDB as well, though we would not recommend this, as a full SQL Server instance offers more functionality.
If your Lansweeper installation is on version 7.2.107.4 or lower and hosted in the Compact database server, you can easily convert your database by following these update instructions. During the Lansweeper update process, your database is converted to LocalDB. This process is automatic and requires no user input.
If your Lansweeper installation is on version 7.2.108.6 or if you only have a SQL Compact lansweeperdb.sdf
file and not a full Lansweeper installation, you will need to manually convert your database.
There are various reasons why you might choose to move from LocalDB to SQL Server:
If required, you can move from LocalDB to a full SQL Server 2014 or newer, any edition.
Test Drive Lansweeper Yourself. Explore our interactive Demo or sign up for free 14-day trial.
Try Now