Hey Vadim,

thanks for the script. however, it presents a bit of a problem when you have multiple instances on a server.

it also does not account for 'other' CPU hogs. i have had to deal with things like anti-virus engines eating up 90% of the CPU. now even though as a DBA, it might not be my job to worry about anti-virus software, i do need to be aware when the SQL server is struggling to process requests because of it.

thanks.