This driver is a stand-alone driver. It provides additional functionality to enable Geo SCADA Expert to interface with specific supported systems or devices. To interact successfully with such systems or devices, you need to:
- Install and run the driver
- Ensure that the driver is licensed
- Configure the required database items and settings on the driver
- Ensure that the database items (and any database items on which they depend) have valid, saved, configuration and are 'In Service'.
-
If you intend exporting the results of any SQL Queries to files that are accessed via UNC paths, ensure that the Windows® user account that the Geo SCADA Expert server uses to export the created files and create any subfolders has the relevant permissions. The particular Windows user account that is used for exporting the results of SQL Queries is that specified for the Printer User (see Printer Settings). This Windows user account has to have permission to create files and folders in the specified share on the specified file server.
Intended Audience
This guide is designed for use by all levels of user:
- Engineers who are responsible for adding and configuring SQL Export items in Geo SCADA Expert
- Operators who use the actions that are specific to the SQL Export driver
- System administrators who are responsible for investigating any unexpected behavior relating to the SQL Export driver.
Document Scope
The SQL Export driver enables you to write SQL queries to interrogate the Geo SCADA Expert database and export the results of those queries to file. The SQL Export driver can export the SQL query results in either Comma Separated Value (CSV) or Tab Separated Value (TSV) format. You define the SQL queries that Geo SCADA Expert is to execute and the format and location to which the results of those queries are to be exported, using fields on the relevant configuration Form—one Form per SQL Query.
This guide explains how to Add and Configure an SQL Export item in Geo SCADA Expert.
It also explains the driver-specific features that are of interest to operators:
and the SQL Export driver specific features may be of interest to system administrators and engineers when investigating unexpected system behavior (relating to the SQL Export Driver):
- SQL Export Specific Status Attributes
- SQL Export Specific Colors
- SQL Export Specific Driver Log File Options.
Prerequisite Reading
This guide contains technical information that is intended for users that are sufficiently familiar with Geo SCADA Expert configuration and operation. Before reading this driver guide, ensure that you are familiar with:
- Geo SCADA Expert configuration practices, procedures, and the configuration of properties that are common to many database items. For more information, see the Geo SCADA Expert Guide to Core Configuration, and the Geo SCADA Expert Guide to Core Point Configuration.
- Driver structure, components, and configuration properties, pick actions, and status attributes that are common to many drivers. For more information, see the Geo SCADA Expert Guide to Drivers.
Some sections of this guide are intended for operator-level users. These sections are intended for users that are familiar with the navigational and operational aspects of Geo SCADA Expert. Before reading the operational sections in this guide, ensure that you are familiar with:
- The Geo SCADA Expert user interfaces (ViewX and Virtual ViewX), the various types of display, their navigation and operation. For more information, see the Geo SCADA Expert Guide to ViewX and Virtual ViewX Clients.
Policy of Continuous Development
To maintain Geo SCADA Expert's position as a leading SCADA solution, we operate a policy of continuous development. Each new version of our product supports additional features and functionality to previous releases. To use the new drivers, features, or functionality involving database items, your system has to be running the latest version of Geo SCADA Expert software. Additionally, if you have upgraded from an earlier version of the product, you have to deactivate any Database Emulation that was activated during the upgrade process. You should only deactivate the Database Emulation once you have successfully completed the upgrade process on all of the servers and clients in your system (see Deactivate Database Emulation after a Successful Upgrade).