Lansweeper data, reports and settings are stored in a database. Your database is hosted in either the Microsoft SQL Compact, Microsoft SQL LocalDB or Microsoft SQL Server database server. As Lansweeper scans and stores a wealth of data, there are many database tables as well.
Though there are hundreds of built-in reports in the Reports menu and more can be found at Lansweeper.com, you may at times want to create your own specialized SQL queries. The Lansweeper report builder is a standard SQL editor, so anyone with knowledge of SQL automatically knows how to use the report builder as well. To help you locate the data you're after, the Lansweeper software has documentation included that explains what each table and field stores.
Accessing the database documentation
To access the Lansweeper database documentation, do the following:
- Make sure your user role includes the Edit Reports permission, as this permission will be required both to access the database documentation and to actually create reports. More information on configuring website access and specifying who has what permissions can be found in this knowledge base article.
- Browse to the following section of the web console: Reports\Database Documentation
- On the resulting page with database documentation, click on a table to jump to that table's documentation. Alternatively, use your web browser's search function (Ctrl+F) to search for specific terms within the documentation.A table you'll likely want to include in any asset report is tblAssets. It stores basic asset details like name, IP address, type etc. A table you'll likely want to include in any ticket report is htblticket. It stores basic ticket details like ticket number, subject, type etc.
Notes on the documentation
Some further remarks regarding the database documentation:
- A link to the database documentation is available within the report builder as well, next to the report title.
- The database contains tables that start with htbl, tbl and tsys. The htbl tables generally store help desk data, the tbl tables asset data and the tsys tables Lansweeper settings. Due to the tsys tables mostly storing settings, which are generally not included in reports, they are not documented.
- The database contains tables that end in Hist, which are not documented. The reason for this is that these tables store historical Windows computer data. They are, with the exception of the Action field, identical to their non-Hist counterparts. A Windows computer's current OS is stored in tblOperatingsystem for instance, while OS changes are stored in tblOperatingsystemHist. The first table is documented, the second one isn't because it's largely the same as the first. History tracking is disabled by default for most scanned data. Information on enabling it and subsequently running reports can be found in this knowledge base article.