Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Session with a high CPU (ms) but no waits---does that matter?


Session with a high CPU (ms) but no waits---does that matter?

Author
Message
Maxer
Maxer
Old Hand
Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)Old Hand (332 reputation)

Group: General Forum Members
Points: 332 Visits: 1603
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)

Thanks!
Erland Sommarskog
Erland Sommarskog
SSC Eights!
SSC Eights! (959 reputation)SSC Eights! (959 reputation)SSC Eights! (959 reputation)SSC Eights! (959 reputation)SSC Eights! (959 reputation)SSC Eights! (959 reputation)SSC Eights! (959 reputation)SSC Eights! (959 reputation)

Group: General Forum Members
Points: 959 Visits: 866
Today, and it has been this way for a decade or more, applicaitons typically connect, run a query, disconnect and rely on the connection pooling the API that a reconnection will be quick. That is, the API lingers to the connection for about 60 seconds, and if there is no reconnection in this period, the API physically disconnects from SQL Server.

However, occasionally you run into application that opens a connection and keeps it open during the lifetime of the application. I may have written one or two myself. It seems that this application's connection back to the metadata database is of this old school. Right or wrong? Since I don't know anything about this application nor about the design decision I am not to judge. I know that in the system I work with, we have components that stay connected.

Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search