Databases

<< Click to Display Table of Contents >>

Navigation:  »No topics above this level«

Databases

Previous pageReturn to chapter overviewNext page

The databases in TeslaSCADA2 are necessary for archiving alarms, operator actions, trends and recipes. When archiving into a database, the subsequent retrieval of data (viewing trends, messages) is much faster, especially over long time intervals. TeslaSCADA2 supports 2 types of databases:

SQLite

MySQL

 

Event database


 The database for collecting events you can setup in Project properties->Events/History tab in Events DB name field. There are several types of events saved in database:

Tag's events. You can setup them in Tag properties->Alarms tab.

Server events. This information about connection, disconnection and lost connection servers in the project.

User login/logout information.

If you setup in User settings it's possible to save user operation.

You can show all events by Events log graphical object from Events library.

 

General history database


 The database for collecting history information you can setup in Project properties->Events/History tab in History DB name field. If you want that tag's history information is saved in this database you have to Enable history in Tag properties->History tab, setup Storage period and check Store in DB.

The history values will be saved every storage period during execution if the value of the tag is changed (if Use deadband is enabled the delta between current value and value last saved should be greater Deadband).

 You can show history information collected in General history database by using Trend DB graphical object from Trends library.

 

History database


 It's another way for collecting history information. The differences between General history database and History database, that is in History database you save only selected tag's values and values are saved in two ways:

Time interval. Tags values are saved every time interval independently values are changed or not.

Tag. Tags values are saved when set tag's value become true independently saved values are changed or not.

You can create history database in Project Window -> Databases or in the menu item Project->New Database of the Main menu.

Tag's value will be saved in the History database if you check Enable history in Tag properties (you no need to check Store in DB in this case) and include this tag in History database properties collection of tags.

       Like for General history database you can use as SQLite as MySQL databases.

 You can show history information collected in History database by using History DB table and History DB trend from History DB library. History Excel Report and History Max and Min Report also work with this database.

 

Recipe database


 The database for working with recipes and parameters. You can create recipe database in Project Window -> Databases or in the menu item Project->New Database of the Main menu.

 Like for events and history databases you can use as SQLite as MySQL recipe databases.

 You can show recipe information collected in Recipe database by using graphical objects from Recipes library.