Hi,

I've got an issue with Priority Manager where any enabled profile setup to run only during working hours causes the Priority Manager service to crash. Symptoms:

- SQL Server held at max CPU usage when profile is triggered
- Service chews RAM to point of failure

When looking at the running SQL process through the SQL2005 Activity Monitor I can see that it floods the SQL server with queries like:

SELECT max(StartTime) as MaxStartTime, Sum(WorkHours) as TotalHours FROM (SELECT DateLineStart, WorkHours, StartTime, (SELECT SUM(WorkHours) FROM tblDateLine WHERE tbl2.WorkHours > 0 AND DateLineStart <= tbl2.DateLineStart AND DateLineStart >= { ts '2010-01-28 15:51:47' }) AS 'Sum' FROM tblDateLine tbl2) M WHERE(SUM <= (10 / 60))

...iterating through the ts value for DateLineStart every second.

Disabling all profiles that run only during business hours allows it to run all other profiles perfectly and doesn't crash out.

- Nathan