Date: Fri, 29 Mar 2024 07:35:59 +0100 (CET) Message-ID: <1493216718.111518.1711694159717@srvdoc.doc.ipesoft.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_111517_552579649.1711694159717" ------=_Part_111517_552579649.1711694159717 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A part of D2000 system is the efficient archiving system (D2000 Industri= al SQL Archive), that provides the following functions:
Each object of Historical value type has a configuration parame= ter specifying the archive history depth. Values older then the depth are a= utomatically deleted. Checking the option Depository cause= s the value to be stored also in depository database. In some cases it may be important to kn= ow that the archive process was not running. For this purpose, the archive = process writes special values with the START and STOP attributes - the opti= on Write Start/Stop must be checked. The option Ar= chive enables/disables writing into the archive database.
The archive subsystem takes care of processing the delayed data. It mean= s, that all dependent values of statistical historical values are recalcula= ted again (e.g. balance calculations) after the arrival of delayed or old d= ata.
To ensure reliability and adequate performance, the archive is optimised=
for the use with Sybase Adaptive Server Anywhere, PostgreSQL and Oracle da=
tabases. Oracle database must be used on the OpenVMS platform (a Sybase por=
t doesn't exist) and is tested for the use in large-scale systems (terrabyt=
e archives). Using Sybase Adaptive Server Anywhere is recommended for archi=
ves under 10 GB when using SQL Anywhere 9.0 and under 50 GB when using SQL =
Anywhere 12.0.
Using PostgreSQL is recommended due to its price-performance ratio for all=
archives ranging from small to large (tested on 2 TB archive database and =
over 12 TB of depository databases).
Besides the databases mentioned above, D2000 system also supports the MS=
SQL server (see the topic Support of MS SQL 2000, MSD=
E 2000, SQL Server 2005 Express and MS SQL 2008 express edition).
For small application with low requirements for the archive subsystem perf=
ormance, it is possible to use a freely available database MSDE (Microsoft =
Desktop Engine) - it is a version of the MS SQL server with limited perform=
ance. For more information on MS SQL and MSDE see the topic Support of MS SQL 2000, MSDE 2000, SQL Server 2005 Express and MS SQL=
2008 express edition.
Note: SQLite and MySQL (and MySQL clones such as MariaD= B and PerconaDB) are also supported experimentally. For more information, p= lease contact Ipesoft.
PostgreSQL settings
Recommended settings for archiving using PostgreSQL database are describ= ed in document PostgreSQL settings for optimal Archive performance= .
Using the standard SQL databases provides the possibility to analyse and= process historical values by means of external tools, e.g. Microsoft Excel= .
Blog articles
Several articles about archiving are available on our blog, currently in= Slovak language only: