The Datasets Module exchanges data with SQL databases and text files. It offers compatibility with various database technologies, including ADO.NET, ODBC, OleDB, and native interfaces. In addition, the module provides straightforward configuration with prominent databases such as SQL Server, Oracle, SQLite, and PostgreSQL.
On this page:
Below is a list of key concepts essential to understanding the Datasets Module.
You need to create a connection for the Datasets Module to communicate with external databases. You can create these connections, called Dataset DBs, by accessing Datasets → DBs in the platform.
In the context of the Dataset Module, a Dataset Query refers not only to an SQL query string but also to a Project object that has a logical name, an SQL query related to that logical name, and other parameters defined within the Datasets → Queries section.
A Dataset Table is a logical name created within a solution to set up access to a specific table in a connected database. These tables are listed in Datasets → Tables. The Tags in the real-time database can easily be mapped to columns in the tables to insert, update, or read operations.
A Dataset File is a logical name that defines parameters for reading and writing files in ASCII, Unicode, or XML formats. To manage the Dataset Files, go to Datasets → Files.
The Datasets Module enables users to interact with SQL databases seamlessly, allowing them to retrieve and manipulate data within their applications. With this module, users can generate custom visualizations using Displays, implement intricate logic using Scripts, and set up dynamic Alarms based on database information. Additionally, the module supports real-time Tags within query strings, adding flexibility to data interaction. It further extends its functionality by managing files and recipes in ASCII, Unicode, or XML formats, making it versatile across various data types.
The Datasets Module forms an integral part of the module, ensuring high performance and seamless integration while exchanging structured data collections in real-time. It efficiently processes data requests from other modules, enabling connectivity with various components such as HMI/SCADA screens, scripting, and reporting tools. It also serves as the data storage configuration hub for other modules. The Alarm and Historian modules, which generate events and records for long-term retention, utilize the Dataset module for defining data storage. Similarly, the Security module can utilize user definitions from an external database within the Dataset module.
Data Source Virtualization is a feature that simplifies data management across multiple data sources. It provides a unified interface for accessing, querying, and manipulating data, regardless of the data storage technology. This feature allows modifications to the data source repositories without impacting the rest of the application. Since the module works with various technologies, you can manage data connections and configurations using a centralized approach, streamlining the integration of different data sources into your solutions.
Access the Advanced Datasets Topics page for more details of how the Dataset module works.
The basic process for configuring the Dataset module is as follows:
The above steps are a simplified explanation of the configuration process. For additional information on configuring the Datasets module, access Configuring Datasets.
To learn more about the Datasets Module, you can use the additional documentation pages available:
The Advanced Datasets Topics page presents complementary information about the following:
Datasets Runtime attributes
Use the Datasets Best Practices and Troubleshooting page to access helpful tips and troubleshooting guides.
In this section: