Siemens Industry Online Support - Automation Service, Automation Support, Simatic...

Page 1 of 10

show the entry list

WinCC -- Configuring Tag Logging -- Archive performance

How can you improve the performance of WinCC Tag Logging (up to WinCC V5.x)?
How can you calculate the required data volumes of the central archive server?
How much hard drive space do messages and process values from SIMATIC WinCC V6.0 or
PCS 7 V6.0 require?
How can you reduce the size of the cyclic storage when using a redundant server pair and
without losing data when changing the archive configuration?
How can you in WinCC reduce the size of the cyclic storage without losing data when changing
the archive configuration?
How does adjusting the system time affect the archiving of alarms, messages and process
values in the Runtime database?

How can you improve the performance of WinCC Tag Logging (up to WinCC V5.x)?
Display part number

Description
In the following is a detailed description of workarounds to determine and optimize the performance of
WinCC Tag Logging. You must execute the three steps one after the other and test accordingly. Keep
the test results in each case so that you can compare them to be able to appraise and evaluate the
improvement.

Note:
The following three steps are valid only for WinCC versions up to WinCC V5.x.

Step 1: Determining the performance of WinCC Tag Logging

You can use an internal system tag from the WinCC Tag Manager as an indicator of the performance
of Tag Logging, the so-called "health display" of Tag Logging. In the process image that contains the
error image described, you display the value of the internal system tag from the WinCC Tag Manager
(e.g. using an I/O field). You monitor the value of this tag over a long period of time (at least one hour
or longer). The value of this tag can be 0 to 50000 decimal. The important thing is that the value
regularly goes back to 0. If value remains greater than 0 for a long period of time (about 5 to 10
minutes or longer), this means that the Tag Logging cannot read values completely from the archive
for reasons of performance. Thus areas of the Tag Logging window in the WinCC Runtime are
displayed as interpolated.

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 2 of 10

Fig. 01

Step 2: Save process value archive (short-term archive) in dBase III format

Storing process value archives (only short-term archives) in the dBase III format improves
performance when archiving Tag Logging values. A short-term archive in the dBase III format is better
for the special user purpose. Subsequently greater volumes of data can be read or archived. In fact
500 measured values can be processed per second.

Proceed as follows for configuring.

Open the Properties (right-click) of the entry "Projectname".mcp in the Tag Logging window - in our
example [spezzw.mcp].

Fig. 02

1. The "Project Properties" dialog window opens. In this window you must enable the option
"Short-term archive using dBase III format" (set check mark in the check box).

Fig. 03
2. Close the dialog box with "OK". Save the Tag Logging and close it too.
3. Then, in the process image that contains the error image described, you observe the system
behavior and check whether the error image occurs again.

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 3 of 10

4. If the error image occurs again, continue optimization with Step 3.

Step 3: Increase the cache of the SQLANY database of WinCC

This gives WinCC the possibility of temporarily storing more Tag Logging values and of reading the
database queue faster. The queue is emptied faster and thus new data can be read from the archive.

Proceed as follows.

1. First, open the Registry of Windows NT via "Start > Run...". Enter the "regedit" command and
acknowledge with "OK".

Fig. 04
2. After calling the Registry, open the following path:
HKEY_LOKAL_MACHINE\SOFTWARE\Siemens\AUTSW\SQLANY
3. If you have a WinCC single-user system, you must change the following settings:
Open the subpath "\...\DBALONE". Change the value of the "EngineCache [2048]" entry from
1000 to 2000 (hexadecimal).

Fig. 05

4. If you have a WinCC multi-user system, you must change the following settings:
Open the subpath "\...\DBSERVER". Change the value of the "ServerCache [2048]" entry from
1000 to 2000 (hexadecimal).

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 4 of 10

Fig. 06

5. Then observe the system behavior in the process image concerned and check whether the
error image occurs again.
How can you calculate the required data volumes of the central archive server?
Display part number

Instructions:
The hard disk requirement of the central archive server is determinated be the space required for the
Tag Logging FAST, the Tag Logging SLOW and the message archive.

The space required by the Tag Logging FAST depends on the archiving settings, the data type
and the time behavior of the values to be archived. The values of Tag Logging FAST are stored
compressed in the database and require approximately 10 to 15 bytes per measured value. In
some cases greater compression is possible.
The values of Tag Logging SLOW require 32 bytes per measured value.
A message with the maximum number of associated values and comments requires 4 KB. The
minimum value for a message is 172 bytes.

Calculation:
You can use the following formula for calculating the maximum memory requirement per second:

Memory requirement [bytes/s] = x * 15 bytes/value + y * 32 bytes/value + * 4096 bytes/value

Where:
x: is the average number of values of the Tag Logging FAST archives per second
y: is the average number of values of the Tag Logging SLOW archives per second
z: is the average number of messages per second

To calculate the space requirement for n days, you can multiply the result of "Memory requirement
[bytes/s]" by the number of seconds in n days.

Sample calculation:
The following is assumed:

No. Assumption Description

1 x = 10,000 values/s Number of values of the Tag Logging FAST archives per second

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 5 of 10

2 y = 10 values/s Number of values of the Tag Logging SLOW archives per second
3 z = 2 values/s 2 messages per second
4 n=5 Number of days, where 1 day = 24 * 3600s = 86400s

Memory requirement in bytes for 5 days = 5 * 86400s * (10,000 values/s * 15 bytes/value + 10

values/s * 32 bytes/value + 2 values/s * 4096 bytes/value)
Memory requirement in bytes for 5 days = 5 * 86400s * (150,000 bytes/s + 320 bytes/s + 8192
bytes/s)
Memory requirement in bytes for 5 days = 5 * 86400s * (158,512 byte/s)
Memory requirement in bytes for 5 days = 68,477,184,000 bytes

Conversion to GB:
Memory requirement in GB for 5 days = 68,477,184,000 bytes / (1024 *1024 *1024)
Memory requirement in GB for 5 days = 63.774 GB
Memory requirement in GB for 5 days 64 GB

From WinCC V6.2:

The calculations set out above apply to WinCC versions prior to V6.2. From WinCC V6.2 onwards,
other calculations apply which generally turn out better than in the older versions because all data is
held in compressed form.
Therefore, the calculation listed above can be referred to as a rough estimate. However, the use of
compression processes means that there is no simply way of telling precisely how much space is
needed from WinCC V6.2.
If special features prompt the need for more space, this is automatically adapted by the WinCC
system. (see Information system: Release notes> Notes about WinCC>WinCC_Runtime)

This entry is also valid for PCS 7 V6.

How much hard drive space do messages and process values from SIMATIC WinCC V6.0 or PCS 7
V6.0 require?
Display part number

Process values:

A measured value in the "TagLogging Slow" archive requires 32 bytes of hard drive memory
capacity
A measured value in the "TagLogging Fast" archive requires about 3 bytes of hard drive
memory capacity (max. 40 bytes depending on compression)

Messages:

Space requirements in the CS-database

A message in a language theoretically requires at least 198 Byte of hard disc space.
A message can theoretically use a maximum value of 5062 Byte.

Each time this value is stored in a segment.

Hard disk space requirements in a RT-Data base

A message without accompaying values and comments requires at least 172 Byte of hard disc
space.

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 6 of 10

A message with the maximum amount of accompanying values and comments requires 4012
Byte of hard disc space.

Note:
From WinCC V6.0 SP4 all data is held in the database in compressed form.
This means that the overall space required for storage is smaller and not easy to calculate. Therefore,
the estimates set out above continue to apply. The information about the memory estimates listed
above can be checked in the WinCC Information System under Information System > Release Notes
> Notes about WinCC > WinCC Runtime > (Note about alarm logging: memory space required for
messages).
How can you reduce the size of the cyclic storage when using a redundant server pair and without
losing data when changing the archive configuration?
Display part number

Instructions:
Entry ID 24195891 gives a general description of how to reduce the size of a cyclic archive without
losing data. The following instructions apply for implementing a redundant WinCC server pair.

No. Procedure
1 Close WinCC Runtime on one computer of the redundant server pair
Deactivate WinCC Runtime on one of the two redundant servers.

Note:
It doesn't matter which of the two servers you deactivate. Before deactivating Runtime, make
sure that the Runtime on the associated redundant partner server functions perfectly.
2 Perform the general steps for changing the archive configuration
On the active WinCC server you execute the instructions given in Entry ID 24195891.

3 Match the configuration on the redundant partner server

There are various methods of transferring the archive and backup configuration to the
redundant partner server without closing WinCC Runtime on the active server.

Reconfigure the archive and backup configuration on the redundant partner server
Make the changes to the configuration (archive and backup configuration) manually on
the redundant partner server.
You don't have to close the WinCC Runtime on the active master for this.

Reconfigure archive and backup configuration on the Engineering Station and load it
onto the partner server
If a separate Engineering Station (ES) is available for configuration, make the changes to
the configuration (archive and backup configuration) manually on the ES. Then you can
load the changed configuration onto the redundant partner server.
You don't have to close the WinCC Runtime on the active master for this.

Duplicate the WinCC project on the partner server using WinCC Project Duplicator
Using the WinCC Project Duplicator you can duplicate the WinCC project of the active
server on the partner server. For this you must close WinCC Runtime on both servers.
Information on the WinCC Project Duplicator is available in Entry ID 22821109.
4 Activate WinCC Runtime on the redundant partner server
Start WinCC Runtime on the redundant partner server.

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 7 of 10

Note:
Once WinCC Runtime starts again on the redundant partner server, a segment change is
performed on the active server. About 15 minutes after the segment change the archive
segments of the active server are copied to the redundant partner for the non-active period.

How can you in WinCC reduce the size of the cyclic storage without losing data when changing the
archive configuration?
Display part number

Instructions:
Under the "Archive Configuration" entry in the Alarm Logging or Tag Logging editor you can set the
size of the cyclic archives (Message archive, TagLoggingFast, TagLoggingSlow). The following figure
shows the "Archive Configuration" dialog with sample settings for the "TagLoggingFast" archive.

Fig. 01

If you change these settings, e.g. reduce the "Max. size of all segments" or the "Time period of all
segments", this can lead to loss of data already recorded.

The following instructions are based on the application described below.

Starting point:
A WinCC system has been archiving process data over a long period of time, a backup of the archive
data has not yet been configured. A very large archive size has been selected, so that space on the
hard disk drive is getting short.

Aim:
Reduce the size of the cyclic archive. Data already recorded should not be deleted or overwritten, but
exported. It should also be possible to display the data of exported archive segments in the form of a
trend or table.

Solution:
The following instructions show the procedure taking the example of the "TagLoggingFast" cyclic
archive. This procedure can also be applied for the other two cyclic archives, "TagLoggingSlow" and
"Message archive". It is not absolutely necessary to close WinCC Runtime for this. If you implement a
redundant WinCC server pair, additional information is available in Entry ID 24197454.

No. Procedure
1 Configure the backup path on the active server
In this step you make settings only in the "Backup Configuration" tab. In this step you must not
under any circumstances change the settings in the "Archive Configuration" tab, because the
data already recorded (archive segments) have not yet been backed up or exported.

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 8 of 10

Open the Tag Logging editor on the active WinCC server. In the left window you select
the "Archive Configuration" entry and double-click on the "TagLoggingFast" entry in the
window on the right. The dialog for configuring the archive and backup of the
"TagLoggingFast" archive opens.
Switch to the "Backup Configuration" tab and make the settings you require.

Fig. 02

Note:
Make sure that "Activate Backup" is checked and that valid destination paths are
specified. Entry ID 24197732 provides additional information on the backup destination
paths.

Apply the settings with the "Apply" button and quit the dialog with the "OK" button.
2 Wait for segment change followed by backup
Wait for the next segment change. The system performs the archive backup 15 minutes after a
timed segment change. Here, all the archive segments not yet exported are copied into the
appropriately configured destination path. Check whether the archive segments have been
copied successfully to the destination paths configured.

Note:
Depending on the currently active archive configuration it might take some time before the next
timed segment change is executed.
Information on segment change is available in Entry ID 22273427.
3 Change the archive configuration
Now you can change the archive and backup configuration (Fig. 01) to meet your requirements.
Apply the settings with the "Apply" button and close the dialog with the "OK" button.

Notes:

Changes in the archive configuration only become effective after the next segment
change.
Depending on the current size of the cyclic archive and the archive configuration, old
archive segments are deleted or overwritten upon segment change.
4 Reincorporating archive segments
To continue to have the data of deleted archive segments displayed at Runtime you link the
exported segments with the Runtime database. Information on the topic of linking exported
archive segments is available in Entry ID 40347325.

How does adjusting the system time affect the archiving of alarms, messages and process values in
the Runtime database?
Display part number

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Simatic... Page 9 of 10

Configuration Notes:
Alarms, messages and process values are saved in the Runtime database with the time stamp of the
WinCC server if the polling procedure is used for archiving. Operator input messages triggered by
WinCC clients are save in the database with the client's time stamp.

Changing the system time of the WinCC computer might have negative effects on the archived data:

Through the segmentation of the Runtime database from WinCC V6 it cannot be excluded that
Runtime data is lost if the system time is changed.

Cause:
From WinCC V6 the Runtime database is saved in the "TagLoggingFast", "TagLoggingSlow"
and "AlarmArchive" archives. The data is stored in segments in these archives. You can define
the maximum size and period for each segment. The Runtime data is stored in a new segment
if the maximum size or maximum archiving period of a segment is exceeded. For an archive
you can define the overall maximum size and overall maximum period for all the segments. If
the overall maximum period or the overall maximum size for all the segments is exceeded, the
oldest segment is overwritten.

Furthermore, changing the system time back and forth can have the undesirable effect that
"old" data is displayed in the "WinCC Online Trend Control" when Update is activated.

Archive synchronization might be affected when using the WinCC "Redundancy" option.

It is therefore strongly recommended to avoid time jumps in the system or when the plant is running.
You should install time synchronization.

After the commissioning phase of a plant there is often the wish to manually set the time in the
system, for example to test the time synchronization or the daylight saving changeover. Please note
here the possible negative effects on the data stored to date described above. Here are a few notes
on this topic:

Doing a complete data backup of the WinCC project

It is advisable to do a complete data backup of the project (including the Runtime data) before
manually triggering a time jump. Once the test has been completed, you can then access the
"clean" Runtime database.

Resetting the system time

It is possible to run tests with the system time in an "old" time window, so that the data
recorded in the test time period is deleted again automatically. For this you must reset the
system time for the test according to the archive configuration (overall maximum period for all
segments). If the system time is put forward again after the test, the data recorded during the
test period is deleted from the Runtime database.

Manual deleting of Runtime data

Notes on manual deleting and resetting of the Runtime data are available in Entry ID
17853608.

Entry ID:29442950 Date:2009-12-21

My tags : Create new bookmark/tag

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012
Siemens Industry Online Support - Automation Service, Automation Support, Sima... Page 10 of 10

I regard this article.... as helpful as not helpful

Copy link Suggestion for the entry Send to a friend

Print

© Siemens AG 2012 - Corporate Information - Privacy Policy - Terms of Use

https://support.automation.siemens.com/WW/llisapi.dll?func=ll&objid=29442950&no... 10/4/2012