I am using Idera's SQL diagnostic manager. It is throwing an alert saying a session has a high CPU (ms) count.
The session has been connected for over 11 hours...however, it isn't really "doing anything". (No wait time, wait types, resources, etc... and no blocking caused by the session)
We have a 3rd party application which has a database on that server. The connection is from that application back to its "meta data database". Every time an action is performed by or against this 3rd party application it has to query its meta data database to determine how to respond.
From what I can tell it is just leaving that session open because every few seconds or minutes an action is being performed.
Is there something "inherently" wrong with an application having a semi-perpetual connection like that?
(If there is a blog post or article which covers this then I would be most appreciate of a link to it so I can better educate myself)