I have been monitoring our episerver site and noticed that one query in particular creates high IO and heavy load on the CPU.
The Query in question is:
SelectCONVERT(NVARCHAR(40), pkID) AS pkID, Name, CONVERT(INT,Enabled) AS Enabled, LastExec, LastStatus, LastText, NextExec,[DatePart], Interval, MethodName, CONVERT(INT,fStatic) AS fStatic, TypeName, AssemblyName, InstanceData, IsRunning, CurrentStatusMessage, DateDiff(second,LastPing,GetDate()) as SecondsAfterLastPing FROM tblScheduledItem ORDER BY Name ASC
We have both a test environment and a production environment, but one should think that the test-environment should be less loaded but in this case it is the test-environment which takes most cpu-time from the database.
It would be great to know how to, atleast, execute this query less often to ease up on the server.
Is it possible that adjusting the different jobs (the ones you can see in admin mode, under planned jobs) that run automatically in Episerver to not run as often as they do by default would help?
Hello
I have been monitoring our episerver site and noticed that one query in particular creates high IO and heavy load on the CPU.
The Query in question is:
Select CONVERT(NVARCHAR(40), pkID) AS pkID, Name, CONVERT(INT,Enabled) AS Enabled, LastExec, LastStatus, LastText, NextExec,[DatePart], Interval, MethodName, CONVERT(INT,fStatic) AS fStatic, TypeName, AssemblyName, InstanceData, IsRunning, CurrentStatusMessage, DateDiff(second,LastPing,GetDate()) as SecondsAfterLastPing
FROM tblScheduledItem
ORDER BY Name ASC
We have both a test environment and a production environment, but one should think that the test-environment should be less loaded but in this case it is the test-environment which takes most cpu-time from the database.
It would be great to know how to, atleast, execute this query less often to ease up on the server.
Thank you
Marcus