1/6/2025 10:13 AM | |
Joined: 9/3/2008 Last visit: 8/19/2025 Posts: 938 Rating:
|
Hi, The problem you have is probably a performance issue. If you look at this FAQ: How many single segments can be connected to the SQL server in PCS 7 without impairing performance? It describes the maximum number and size of segments that WinCC can handle. The total number of segments are 200. This total means Alarms + Taglog Fast + Taglog Slow. In your project you have set it to about 400 segments just for Taglog Fast. So I suggest you change the single segment size to perhaps 1 week if you want to keep 14 months. This would give you about 56 segments (1 month = around 4 weeks) * 14 = 56. You just need to do the same with Taglog Slow if you have data in this archive. If you have no tags logged here, you can just set it to one month or so. The alarmlog is event driven since alarms/events are triggered when something happens instead of on intervals, so here you will need to see on the filesize what is best and also how long back in time is needed. Also remember that you can activate backup of the segments so you can attach segments manually if necessary and detach them when you don't need them. About the size (250 GByte), then WinCC will monitor the archive for the total size and if the size exceeds this before the total time you set, then the oldest archive will be overwritten. I hope this helps. Best regards Michael |
Michael |
|
This contribution was helpful to
2 thankful Users |
1/17/2025 2:25 PM | |
Joined: 1/6/2025 Last visit: 9/2/2025 Posts: 2 Rating:
|
Thanks for your answer! I haven't considered maximum segments. 14 months and one segment per day would make 400+. I will try to modify it.
|
Follow us on