Ok, yes, then if there is no DSN listed in the client variables page, that confirms that you cannot possibly be using them (whether intentional or otherwise). Glad to see that ruled out.
The query logging (and analysis) would seem to be the useful next step-though again, 100% CPU in the DB sure sounds like something that could be observed with monitoring on the DB side. It may not even be CF's fault that it's being stressed so. But if you can't get the DBA to consider that, then the next best thing is to see if the query logs may show whether in fact CF is stressing the DB (whether in terms of the number or duration of queries, especially around the time that the 100% CPU issue is being reported). Will look forward to hearing how things sort out. /charlie From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf Of Barry Chesterman Sent: Monday, November 29, 2010 3:41 PM To: cfaussie@googlegroups.com Subject: Re: [cfaussie] Re: Microsoft SQL server CPU very high, close to 100% a lot of the time Hi Charlie, I have checked our client variables pages and there aren't any DSN's listed (just the default option of registry selected), I've checked the cfapplication tag for the site too and it uses the default (registry). I'll log full query stats for a day anyhow and see if it shows us anything interesting :) Regards Barry. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
