SQL Database Export plugin for Data Loggers

Latest version: 5.0.1 build 1126. November 28, 2025.

The SQL Database Professional module enables direct export of parsed data from all our data loggers into major SQL servers such as Oracle, Microsoft SQL Server, MySQL, PostgreSQL, DB2, Informix, Sybase, Interbase, Firebird, and SQLBase. It uses vendor driver interfaces when available and falls back to ODBC for unsupported servers. This approach reduces client overhead and network traffic and permits use of database-specific features such as stored procedures, custom types, and native transaction handling.

Download demo | PDF manual | Buy Now!

Why choose direct driver export

Direct driver access reduces system requirements by avoiding intermediary layers and decreases traffic between client and server. It also exposes server specific capabilities. For example, Microsoft SQL Server stored procedures can encapsulate validation logic, and Oracle functions can transform values before insert.

SQL queue and multi-statement workflows

Use the SQL queue when data export requires multiple steps. A queue executes statements in order; SELECT results can populate variables that feed subsequent INSERT or EXECUTE statements. This design reduces the need for complex nested SQL and allows inserting data without stored procedures. Queue items accept parameters like :P1 which map to parser variables or predefined values (NULL, DEFAULT).

Practical example 1: Insert with lookup

Scenario: The device sends sensor readings with a sensor ID. You need to ensure a sensor record exists and then insert a reading referencing that sensor id. Configure a two-statement queue:

1) SELECT sensor_pk FROM sensors WHERE device_id = :P1; (returns SENSOR_PK)
2) INSERT INTO readings(sensor_id, value, timestamp) VALUES(:SENSOR_PK, :P2, :DATE_TIME_STAMP);

Parser variables: P1 = device_id, P2 = sensor_value. If the SELECT returns null, use a default or execute an INSERT into sensors first. This example shows how SELECT output feeds the subsequent INSERT using the preconfigured SQL queue.

Integration example with Advanced Serial Data Logger

Incoming data from a serial device (ASCII record):

ID=42;VALUE=7.1;TS=2025-01-02 08:00:00

The ASCII parser configuration extracts variables: DEVICE_ID → 42, SENSOR_VALUE → 7.1, and DATE_TIME_STAMP → 2025-01-02 08:00:00. The SQL queue uses parser variables and sends them as parameters to an SQL server:

INSERT INTO readings(sensor_id, value, created_at) VALUES (:DEVICE_ID, :SENSOR_VALUE, :DATE_TIME_STAMP)

Key features

Direct vendor driver support for Oracle, MSSQL, MySQL, PostgreSQL, and more.
SQL queue for multi-statement workflows with parser variable passing.
Connection modes: persistent, per transaction, disconnect when inactive
Error handling with temporary local buffering and configurable automatic restore.
Custom connection attributes including SSL, timeouts, and server port number.
Ability to execute stored procedures and send returned data back to devices.

Summary

SQL Database Professional gives precise control over exporting parsed data to SQL servers using direct drivers or ODBC as a fallback. Use SQL queues to implement multi-step workflows, stored procedure calls for server-side processing, and robust error handling for reliable data delivery.