In addition to the standard tables, the Database Schema includes a set of tables that are not associated with specific classes. You can use these tables to display a range of useful information from the database.
Query Processor Tables
- CAlarm—This table allows you to obtain a snapshot of the alarm information within the database.
- CAreaOfInterest—This table allows you to list the Areas of Interest within the database. This table only applies if the Area of Interest feature is enabled on your system (see Enable or Disable the Area of Interest Feature in the ClearSCADA Guide to Server Administration).
- CDynacardStoreLatestView, CDynacardStoreView, CDynacardView—These tables allow you to access the uploaded Dynacard data from Rod Pump controllers (for example, Lufkin controllers) that is stored in Dynacard Store items.
- CForecastHistoric—This table allows you to access the historic data generated by forecast items.
- CLicense—This table shows how many points and clients are licensed on the server on which you run the query. The table also shows how many Dream Report components are licensed on that server.
- CSeverity—This table allows you to list the details of the severities that are configured in the database.
- CSystemStatusTable—This table allows you to list the status details of server and driver modules in the database.
- CTextAlarm—This table allows you to list text alarms. You can search the table and acknowledge text alarms by reading alarm cookie numbers and executing methods to acknowledge alarms based on alarm cookie numbers.
Historic Tables
- CDBAlarmSummary—This table allows you to access a combination of current and historic alarm information within the database. This table only applies if the Alarm Summary feature is enabled on your system (see Enable or Disable Alarm Summary Data in the ClearSCADA Guide to Server Administration).
- CDBAlarmSummaryFile—This table allows you to list information about Alarm Summary files, including the number of records and the start time of the file. This table only applies if the Alarm Summary feature is enabled on your system (see Enable or Disable Alarm Summary Data in the ClearSCADA Guide to Server Administration).
- CDBConfigChanges—This table allows you to list event information from the Configuration Changes records. This table only applies if the Configuration Changes feature is enabled on your system (see Configuration Changes Auditing in the ClearSCADA Guide to.Server Administration).
- CDBConfigChangesFile—This table allows you to list information about historic Configuration Changes Files including the number of records and the start time of the file.
- CDBEventJournal—This table allows you to list event information from the Event Journal (see Historic and Archive Data).
- CDBEventFile—This table allows you to list information about Event Journal Files, including the number of records and the start time of the file.
- CDBHistoric—This table allows you to access data (such as that for points and master station accumulators) that is stored historically in the database. ClearSCADA only stores data historically for those database items for which Historic is enabled and the data meets the historic storage criteria. For more information, see Defining Historic Details for a Point in the ClearSCADAGuide to Core Point Configuration.
- CDBHistoricAll—This table allows you to access data (such as that for points and master station accumulators) that is stored historically in the database. This particular table provides access to 'Put Aside' data that is stored historically in the database, following a point override. For more information, see Store Put Aside Values Historically in the ClearSCADA Guide to Core Point Configuration.
- CDBHistoricFile—This table allows you to access information about the reports and other documents that are stored historically in the database. This table only applies if the Historic Files feature is enabled on your system (see Enable or Disable Historic Files in the ClearSCADA Guide to Server Administration).
Always restrict the amount of data that you query in a historic table. This will help to reduce any adverse affects on the communications on your system, caused by a query attempting to retrieve large amounts of historic data from the server.
When restricting a query by time, use the RecordTime field in a historic table, rather than the Time field (as 'Time' is a reserved word in SQL).
Metadata Tables
- DBDictionary—This table allows you to access the user dictionary to query or update user translations for the ClearSCADA databases.
- DBTableDef, DBFieldDef—These tables allow you to access database metadata information by using a query. The tables provide the same information that is in the database schema.
- DBEventCategoryDef—This table allows you to access information about predefined event categories in the database.
- DBAlarmCondDef—This table allows you to access information about predefined alarm conditions in the database.
Further Information
You can use the ClearSCADA Database Schema to display a list of the available tables (see Working with the Database Schema).