Promotic

Data saving into the one table of the PostgreSQL database (Database PostgreSQL cyclic) - configuration window

Description:
The window serves for setting the parameters for the data storage into the PostgreSQL database. By this technology the data are stored into the one table (in the PostgreSQL database) with the name specified in the "Table" configurator. The minimum and maximum size of the table is defined. If the current size of the table exceeds the maximum size, then so many oldest records are removed to decrease the size to the minimum size of the table. This walkthrough repeats all over again.
By the RunTime method it is possible to do backward writing for this type of setting the storage (it is possible to write the records with the older time than the time of the last written record).
By this technology the writing is performed by means of the ODBC driver for the PostgreSQL database, which has to be installed to the computer were the PROMOTIC application is running.
Configurators:
Data source (ConnectionString)The ADO ConnectionString (http://www.connectionstrings.com) contains all necessary parameters needed by the ADO Connection object for database connection via the selected ADO Provider.
Macro expression can be used for input (it is evaluated after the application is launched). This configurator must not contain an empty string. For example Provider=MSDASQL;Driver={PostgreSQL UNICODE};Server=localhost;Port=5432;Database=pm_data;Uid=pm_admin;Pwd=pmadmin;
Additional parametersAdditional parameters for storing. Allows to define names and data types of system columns, database types based on the trended value data type. Available parameters are shown in the following example together with their preset values for selectaed saving type (plugin). These values may not be entered. Enter the values only if non-default are needed. Entries are in the KeyVal format, for example "coltimename:pm_time;colattrname:pm_attr;dbdt.pmtime:TIMESTAMP(3);dbdt.pmattr:SMALLINT;dbdt.f64:DOUBLE PRECISION;dbdt.f32:REAL;dbdt.i32:INTEGER;dbdt.i16:SMALLINT;dbdt.u8:SMALLINT;dbdt.b:BOOLEAN;".
Macro expression can be used for input (it is evaluated after the application is launched).
coltimename (optional) - Name of the column containing the record timestamp.
Default "coltimename:pm_time;".
colattrname (optional) - Name of the column containing the record attribute.
Default "colattrname:pm_attr;".
dbdt.pmtime (optional) - Database data type of the column containing record timestamp.
Default "dbdt.pmtime:TIMESTAMP(3);".
dbdt.pmattr (optional) - Database data type of the column containing record attribute.
Default "dbdt.pmattr:SMALLINT;".
dbdt.f64 (optional) - Database data type of the column for trended variable of the data type: Float64 (Double).
This is used if the trended value does not have its database data type defined.
Default "dbdt.f64:DOUBLE PRECISION;".
dbdt.f32 (optional) - Database data type of the column for trended variable of the data type: Float32 (Single).
This is used if the trended value does not have its database data type defined.
Default "dbdt.f32:REAL;".
dbdt.i32 (optional) - Database data type of the column for trended variable of the data type: Int32 (Long).
This is used if the trended value does not have its database data type defined.
Default "dbdt.i32:INTEGER;".
dbdt.i16 (optional) - Database data type of the column for trended variable of the data type: Int16 (Integer).
This is used if the trended value does not have its database data type defined.
Default "dbdt.i16:SMALLINT;".
dbdt.u8 (optional) - Database data type of the column for trended variable of the data type: Uint8 (Byte).
This is used if the trended value does not have its database data type defined.
Default "dbdt.u8:SMALLINT;".
dbdt.b (optional) - Database data type of the column for trended variable of the data type: Bool (Boolean).
This is used if the trended value does not have its database data type defined.
Default "dbdt.b:BOOLEAN;".
TableName of the table in the database into which the data are stored.
Macro expression can be used for input (it is evaluated after the application is launched). This configurator must not contain an empty string.
Minimum table sizeMinimum size of the table specified by the records count. The number of records in the table never drops below this minimum limit.
Maximum table sizeMaximum size of the table specified by the records count. The number of records in the table never exceeds this maximum limit. When exceeding this limit, such count of the oldest records is removed to decrease the number of records in the table to the minimum size of the table.
The -1 value means that the maximum size of the table is not limited by the records count.
Minimum table size by time spanMinimum size of the table specified by time span. The time span of records in the table never drops below this minimum limit.
Maximum table size by time spanMaximum size of the table specified by time span. The maximum time span of all records in the table. When exceeding this limit, such count of the oldest records is removed to decrease the number of records in the table to the minimum size of the table.
The -1 value means that the maximum size of the table is not limited by the time size.
Note:
If the writing operation of record to the database fails, then the PROMOTIC system will try to write the record two more times. If the writing operation of record fails because of network error (timeout), then the PROMOTIC system closes the connection and will try to connect and write the record during following writings (of the same or another record). If the connection is regained, then the writing of trend records continues automatically. If the network failure continues during a longer period of time, some records may be lost. The information regading writing errors on network failure will be written into the global errors of the INFO system.

History:
Pm9.00.03: Created
PROMOTIC 9.0.27 SCADA system documentation MICROSYS, spol. s r.o.

Send page remarkContact responsible person
© MICROSYS, spol. s r.o.