Dear,

We are using WinCC Professional for a while and we are running into problems that WinCC is very slow at startup (needs 45minutes). It looks like PC is in IDLE because CPU < 10% usage, HDD < 5%, Memory 8gb (16 gb free).

When i look to the activity monitor of the Microsoft SQL Server i see the same behavior Processor time <10%, Waiting taks 0, Database IO 1,4 MB/Sec.

WinCC settings:

Alarm and events;

Time period of all segments : 1 years

Maximum size of all segments: 20GB

Time period contained in a single segment: 1 days

Maximum size of a segment: 1gb

Fast data log:

Time period of all segments : 1 years

Maximum size of all segments: 150GB

Time period contained in a single segment: 1 days

Maximum size of a segment: 2gb

Slow data log:

Time period of all segments : 1 years

Maximum size of all segments: 50GB

Time period contained in a single segment: 1 days

Maximum size of a segment: 1gb

The goal is to store the data for one year.

And because the PC is not using any resources it looks strange that it the system is not faster at start up.

My question is;
Can somebody help me by tuning the database and/or settings to make this process faster to load the data at a startup?

Thank you.

Best regards

Robert

Hello,

When the WinCC Runtime takes so long to start, you have to pay attention to which of the processes stops the longest. If it is in the AlarmLogging or the TagLogging the issue will be in the database. It is recommended to review these points:

Activating WinCC Runtime freezes during Alarm/Tag Logging

Hi Robert

You describe that all three logs are set to 1 single segment pr day and one year. This would mean that you in worst case would have 3 * 365 segments.

WinCC can max handle 200 segments so you have to change this setting.

Possibly 1 week pr segment.

Best regards

Michael