Well, as far as having the limits because you've not needed to use it, I'm proposing that now's the time. :-) And after capturing that data, then look in the JDBC logs (which are not enabled by default-again, controlled in the jdbc settings page). It's going to be a lot of data, but you can do all sorts of things to analyze it, whether using Excel (or Open Office Calc) or the free Microsoft Log Parser tool. There is a technote from Intergral on using Excel to analyze the FR logs (http://www.fusion-reactor.com/support/kb/FRS-161.cfm), and I have a page I created with lots of info on analyzing them using LogParser (http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-3).
For instance, just getting a count of queries happening per minute can help (you can also interpolate that from the resource log instead, since it has a count of queries that finished every 5 seconds). But you could go further and report things like how many times specific queries are running, etc. As for the DBA being "fairly certain" in his assertion, this is one of those times where analysis of diagnostics should be trusted more than intuition. I make a living help people find and correct such misconceptions. :-) As for the client var question, the first step is simply to look in the CF Admin, on the Client variables page, to see if any DSNs are listed. Are you able to do that, or are you perhaps not allowed to access the Admin? Just can't tell what you're conveying in only being able to guess at things (it's your Monday workday for you guys, right, so I'm assuming it isn't that you're not at work). :-) As always, just trying to help. /charlie From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf Of Barry Chesterman Sent: Sunday, November 28, 2010 8:25 PM To: cfaussie@googlegroups.com Subject: Re: [cfaussie] Re: Microsoft SQL server CPU very high, close to 100% a lot of the time It is looking like a 'death of a thousand cuts' issue as you put it, and we do have a plan if that is the case :) We have limits on the JDBC stuff in fusionreactor because we haven't really needed to use it. Our DBA is fairly certain that there isn't a set of, or a specific query that is causing a problem. All of our datasources are indeed wrapped. As far as I know, we don't have any DSN set to a client variable datasource. -- 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.
