A system only needs to run the ClearSCADA ODBC driver in order for ClearSCADA to transfer data to and from another database, using ODBC.
It is also possible for other applications to use ODBC to access the ClearSCADA database. This section summarizes the requirements that enable other applications to access the ClearSCADA database in this way.
In order for other applications to access the ClearSCADA database using ODBC, you need only install the appropriate Data Access components of ClearSCADA on the client computer (the computer that is running the application that is to access ClearSCADA using ODBC). (If the client computer is to run as a full ClearSCADA client, as well as run the other applications that are to access ClearSCADA using ODBC, you also need to install the appropriate ClearSCADA Client components.)
Where applications do not have a separate user account, access is via ClearSCADA’s Guest User account (see Configuring the Guest and Web User Accounts in the ClearSCADA Guide to Security).
The ODBC data access interface can be used to access Historic Pseudo tables within ClearSCADA. For information on the fields that these tables contain, see the database Schema. For information on the database Schema, see Working with the Database Schema in the ClearSCADA Guide to the Database. You can also use ODBC to access the data in 'custom' tables, such as Data Grids. For information on using Data Grids, see Configuring Data Grids in the ClearSCADA Guide to Core Configuration.
You can enable logging to monitor any unexpected system behavior when ODBC is used to access to the ClearSCADA database. For more information, see ODBC Logging in the ClearSCADA Guide to Client Administration.
NOTE: For information on the SQL Queries that have been used to request data from ClearSCADA, view the various Queries categories in the ClearSCADA Server Status Tool’s Query Processor folder (see Server Status Categories in the ClearSCADA Guide to the Server Status Tool).