bg2492

Hello krolig,

there are two different meanings of compressed archives and compressed archivedata
in connection with the Taglogging.

1. There are "normal" Processvaluearchives and Compressed Archives.
   In the Compressed Archives are values stored, which have been calculated
   from the "normal" Processvaluearchives, i.e. one value per hour as mean
   value of the archived values from "normal" Processvalue, which may be archived
   once every minute.

2. With the first version V6.0, when the MS SQL-Server was used with WinCC, there
   was a difference between Taglogging-Slow- and Taglogging-Fast-Archive-Segments
   In the Taglogging-Slow-Archive-Segments the data were stored directly and in the
   Taglogging-Fast-Archive-Segments the data were stored in a compressed manner
   in binary packages. But with the newer versions of WinCC the data in the
   Taglogging-Slow-Archive-Segments are stored in a compressed manner too.
   You can only read out the data with a script by using the WinCC OLE DB Provider,
   which is uncompressing the binary packages.


Regards

Georg Berghof

 Hi bg2492,

May I know if I can uncompress the binary packages via SQL script? The reason being is I am working on report designer, with intention to utilize ODBC table to display my compressed archive value from SQL database. ODBC table allow me to write the SQL query, which give me flexibility in designing my report layout. Now the only issue is I can't display my compressed value because it is shown in binary values. I have gone through the siemens example "Export of archive data using the SIMATIC WinCC/Connectivity Pack (OLE DB Provider)", but it required extra step to uncompress the data into CSV form, which is not suitable for me to directly read the data via ODBC connection. Any suggestions are appreciated. Thanks.

------------------------------------------------------------------------------------------
Split from Tag logging, compressed archives and tags configuring.