Historical Data, Alarm and Event Files in Citadel 5

The LabVIEW Datalogging and Supervisory Control (DSC) Module, version 7, uses the Citadel 5 historical database to store historical data.

This document lists the database file types of the Citadel 5 historical database and the corresponding file types in a Citadel 4 database. In most cases, use the DSC Module database management features, such as the Historical Data Viewer, and the Historical Data VIs to manage Citadel 5 databases.

Historical Data Files

Historical data is contained in the following collection of files:

File Name/Extension Description Citadel 4 Equivalent File
Streaming Data 
cx00000001.cdpg data file(s) .thd
ix00000001.cdib part of page index files .tdx
stridm.cdin     sub-index file .tdx
pid.cdih   header of page index file .tdx

nodetree.elog     nodetree for browsing the database, high-level index file .tdb
nodetree.elog.ckpt0 (or .pt1) raw backup file of nodetree, pt0/pt1 are alternating files
extensions to give maximum robustness .tdb 
nodetree.elog.cpct   compacted backup file of nodetree .tdb, .bak

Alarm and Events Data  
mssql.mdf     SQL Server database for historical alarms and events .ale
mssql.ldf   index file (?) for historical alarms and events .adx
rdbfiles.lst list of MSDE files in detached database n/a

sdb_lock lock file exists when database has active logger n/a

Alarm and Event Files

Alarm and event data is contained in the MSDE SQL Server (relational) database files.

4 Ratings | 3.75 out of 5

 Print |  PDF

Reader Comments | Submit a comment »

mssql.ldf is not index file
the mssql.ldf is a transaction log file which records nearly all tractions to the actual database. when properly maintained, it can be used to restore database to a previous state in situations such as disaster recovery, etc.
- Jul 07, 2011