Promotic

MS SQL backup data saving (Database MS SQL server backups) (obsolete) - configuration window

Description:
The window serves for setting the parameters for the data storage into the MS SQL database. By this technology the data are stored into tables (in the MS SQL) with the name beginning with the same prefix as the trend group identifier.
The size of one table and its maximum number is defined. If one table (backup) in the database is filled up (the size of data in the table exceeds the defined value), then a new table is created into which it is written from this moment. This walkthrough repeats all over again.
The name of the variable on the "Data" tab can be maximum 80 characters long (the length of input editbox is limited).
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 starting the application). This configurator must not contain an empty string. For example "Provider=SQLOLEDB;Server=.\MSSQLSERVER;Database=pm_data;Uid=pm_writer;Pwd=pmwriter;"
Additional parametersAdditional parameters for saving. 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 "dbdt.pmtime:DATETIME;dbdt.pmattr:INT;dbdt.f64:FLOAT;dbdt.f32:REAL;dbdt.i32:INT;dbdt.i16:SMALLINT;dbdt.u8:TINYINT;dbdt.b:BIT;".
Macro expression can be used for input (it is evaluated after starting the application).
dbdt.pmtime (optional) - Database data type of the column containing record timestamp.
Default "dbdt.pmtime:DATETIME;".
dbdt.pmattr (optional) - Database data type of the column containing record attribute.
Default "dbdt.pmattr:INT;".
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:FLOAT;".
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:INT;".
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:TINYINT;".
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:BIT;".
Backup (table) name's prefixThe first part of the backup name (of the database table). The whole backup name consists of this prefix followed by a serial number.
The backup names creation can be modified in the onBackupCreate event, i.e. using self defined backup names.
Macro expression can be used for input (it is evaluated after starting the application). This configurator must not contain an empty string.
Backup creation is defined by records countIf checked, then the backup (creating new file) is performed on achievement of specified record number. If not checked, then the backup size is not limited by record count.
Number of recordsThe size of one backup (i.e. table) is defined by the record count.
If the backup size defined here is exceeded when writing new record, then new empty table is created and the new record is saved here. Following records are saved into this new backup since this moment.
Backup creation is defined by time-spanIf checked, then the backup (creating new file) is performed periodically with the defined period (every year, month, week, day, hour, minute). If not checked, then the backup size is not limited by time range.
Time-spanThe backup (i.e. table) size is defined by time-span.
If the backup time-range in the table defined here is exceeded when writing new record, then new empty table (*.dbf file) is created and the new record is saved here. Following records are saved into this new backup since this moment.
1 year
1 month
1 week
1 day
1 hour
1 minute
Backup count is limitedIf checked, then the maximum number of the backup count is limited. If this number of files is achieved, then the oldest backup file is replaced by the newest one. If not checked, then the backups count is not limited.
Maximum number of backupsMaximum number of backup files. By continual writing, new tables (backups) are created. Their maximum number is defined by this configurator. If there is defined, for example, the maximum number of backups to 10 and 11th backup is created, then the backup with the oldest data is removed and the backups count is still only 10.

History:
Pm8.03.00: The "Data source (ConnectionString)" configurator modification.
Pm8.02.01: Obsolete
PROMOTIC 9.0.22 SCADA system documentation - MICROSYS, spol. s r.o.

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