max size of History DB

[johanningmann]

Hello,
does anyone have real live experience in regards to the database size which WinCC OA can handle without any performance issues. We trying to figuring out how often we have to Backup the DB and how much GigaByte is practical to handle by Win CC OA. We looking for a good way to find the balance between having the data available for trend and other live system features and swap files. Is there a guidance available or some real live experience what is practical and functional in a perform manner?

e.g.
We run our System 3.15 P7 now for 2,5 years all archive only run with compression Level 1 (Due to the reason that we have to correct value in the database).

Our db-folder has now a size of 176GB.

We plan to connect a lot more system nodes to the distributed system, which will end up in more data for the central server.

We would appreciate some experience or ways of how to handle such system.

Kind regards
Frank Johanningmann

[leoknipp]

You can follow the given information to optimize the database:
-- DP elements with a similar change rate shall be saved in one archive.
The fill grade you can easily check by comparing the size of uncompressed and compressed files.
-- The size of new archive files shall not be the maximum of 2 GB.
-- Reduce the number of files in the database to the required minimum.
At every startup the archive managers has to check the state of the existing files in the VA directory. If there are more files present it can take longer.

For accessing historical data it does not make a big difference if there are more file available as only the files which cover the requested time range are opened and read.

Best Regards
Leopold Knipp
Senior Support Specialist

[johanningmann]

Hi Leopold, thank you for the answers.


Kind regards
Frank Johanningmann