LNDB LoggerNet Database Software
Valuable Tool
Use standard database tools on LoggerNet data
weather applications water applications energy applications gas flux & turbulence applications infrastructure applications soil applications

Overview

Current Version: 1.3

LNDB is an application that enables you to easily move data from a LoggerNet data cache into a database such as Microsoft SQL Server or MySQL. Then you can use industry-standard software to access and query your data for reports. LNDB also comes with QuickReports, an application that allows you to generate simple reports from an LNDB database with just a few mouse clicks.

Read More

Benefits and Features

  • Moves data from selected LoggerNet tables into a database
  • Imports data from a data file into a database table
  • Exports data from a database table into a data file
  • Includes QuickReports application to design simple reports from an LNDB database
  • Allows you to review database data
  • Monitors the LNDB Engine

Images

Detailed Description

LNDB has two main components: LNDB Manager and LNDB Engine. LNDB Manager is used to set up a database and select the datalogger data tables that will be stored in the database. It also provides tools to monitor the LNDB Engine and to review the database data.

LNDB Engine runs as a service and sends the selected data from the LoggerNet data cache to the database. Additionally, LNDB includes utilities for importing and exporting data, and generating simple reports from your database data.

Specifications

Current Version 1.3
Operating System Windows 10, 8, or 7

Compatibility

Supported Databases

LNDB has been tested and shown to work with the following databases:

  • Microsoft® SQL Server® (Express, Standard, and Enterprise) 2005–2016
  • Microsoft® SQL Server® Compact 3.5 SP2
  • MySQL 5.0–5.7 (with an appropriate 32-bit ODBC database driver; for example, MySQL 5.0 or 5.1 with MySQL 3.51.27 or 5.1.6 ODBC database driver, note that earlier versions of 5.x ODBC database drivers have known issues; MySQL 5.6 with MySQL 5.3 ODBC database driver)

Note: LNDB may work with other versions of SQL Server Express, SQL Server Compact, or MySQL.

Computer Requirements

LNDB runs on Windows® 10, 8, or 7.

Datalogger Considerations

Compatible Contemporary Dataloggers

CR200(X)
Series
CR800/CR850 CR1000 CR3000 CR6 CR9000X CR300
Series
CR1000X

Compatible Retired Dataloggers

CR500 CR510 CR10 CR10X 21X CR23X CR9000 CR5000 CR7X

Downloads

Getting Started with LNDB Tutorial (pdf format) v.- (4.58 MB) 10-18-2010

This tutorial shows how to move data into a database using LNDB. The report generation capabilities of QuickReports are introduced and we show how to use a database as a data source in RTMC Pro.


LNDB Patch v.1.3 (41.8 MB) 12-22-2017

Upgrades LNDB 1.x and 1.2 to 1.3.

Note: This application requires the Microsoft .Net 4.0 Framework.  If it is not already installed on your computer,  it can be obtained from the Microsoft Download Center.

View Update History

LNDB Trial v.1.3 (41.8 MB) 12-22-2017

A fully functional 30 day trial version of LNDB (LoggerNet DataBase) software.

Note: This application requires the Microsoft .Net 4.0 Framework.  If it is not already installed on your computer,  it can be obtained from the Microsoft Download Center.

Frequently Asked Questions

Number of FAQs related to LNDB: 25

Expand AllCollapse All

  1. The LNDB service runs under a local system account by default, which may be why it uses the computer name. Go to Control Panel | Administrative Tools | Services and set it to run under a user name.

  2. One method is to use Custom Collect to specify a range of data and then store the data to a different file. Alternatively, if LNDB is set up to store data in a database, a range of data can be pulled out and stored in a separate data file. These two methods, however, are manual ones.

  3. No. LNDB works independently of Baler.

  4. The easiest way to get the data into LNDB is to store the information in the LoggerNet data cache (or, for the information to be in a format that looks like a datalogger data file to LNDB so that it can be imported).

  5. LNDB uses two fields as primary keys: the record number and time stamp. If the record number and time stamp are both duplicated, the record is discarded. If only the record number or only the time stamp is duplicated, LNDB should import the record. 

  6. No. For information about creating live connections to Microsoft SQL Server, Oracle, or MySQL data sources with FileMaker Pro’s External SQL Data Source feature, visit the FileMaker website.

  7. Table names in LNDB are automatically generated and cannot be changed.

  8. Not at the same time. Currently, a user would have to manually switch back and forth between the database hosts periodically using the File menu Select Database... option to keep them both updated.

  9. LNDB currently requires that all datalogger table columns have a corresponding database table column. There are currently three options when table definitions change:

    1. Stop Storing Data (The user can manually alter/archive the database table.)
    2. Archive Database Table
    3. Modify Database Table (New columns are added, and old columns are orphaned. If the database column data type is not what is expected, an archive occurs.)

Case Studies

Delaware River: Bridge Health
Intelligent Infrastructure Systems, a Pennoni company, was contracted to design and install an efficient structural-health......read more

Listed Under

Common Accessory for the following products: