Hi all,

today we took offline for mantainance tasks the SQL Server containing our K2 Blackpearl databases (we have one server for the K2 Blackpearl host server and another for the SQL Server).

After 15 minutes, logging on the server hosting the K2 Blackpearl engine, I've noticed that the K2 Blackpearl process was eating 90% CPU and logging 30MB/min of "unable to connect to SQL Server" errors (about 450MB of logs in 15min of SQL Server inactivity).

Here's the question: how to avoid K2 blackpearl service going in a log-loop when SQL server has connectivity problems? Is there some configuration to do?

If SQL server one night goes offline for some reason, the server hosting (also) the K2 engine could freeze, because of CPU load and lack of disk space...

Regards,
Fede