h the "exec sp_execute 162, 5909,
> 1973" stuff.
>
> Thanks
>Mark
>
> -Original Message-
> From: Gert Franz [mailto:gert.fr...@railo.ch]
> Sent: Thursday, February 12, 2009 10:58 AM
> To: cf-talk
> Subject: AW: (ot) More SQL Profiler questions
&g
On Thu, Feb 12, 2009 at 10:22 AM, Gaulin, Mark wrote:
>
> Say, what was the deal with going "back to using the regular SQL Server
> JDBC" and "my queries are flying"?
My fusion reactor wrapper driver was misconfigured... I'd accidentally
referred to the FR2.0 documentation for setting it up... s
"exec sp_execute 162, 5909, 1973"
stuff.
Thanks
Mark
-Original Message-
From: Gert Franz [mailto:gert.fr...@railo.ch]
Sent: Thursday, February 12, 2009 10:58 AM
To: cf-talk
Subject: AW: (ot) More SQL Profiler questions
Well in Railo in the debugging info you always get t
cements to Adobe/macromedia on how
they could help this situation, for whatever good that has done. (None,
I suppose.)
Thanks
Mark
-Original Message-
From: Rick Root [mailto:rick.r...@webworksllc.com]
Sent: Wednesday, February 11, 2009 5:57 PM
To: cf-talk
Subject: (ot) More SQL P
nt: Thursday, February 12, 2009 10:04 AM
To: cf-talk
Subject: Re: OT: More SQL Profiler questions
In case anyone else comes across this via google...
Once a query is compiled with sp_prepare, it is stored in a system table
however only the first 128 characters of the SQL are stored in a visible
In case anyone else comes across this via google...
Once a query is compiled with sp_prepare, it is stored in a system
table however only the first 128 characters of the SQL are stored in a
visible form in SQL 2000
The easiest way to handle this was to set MaxPooledStatements to 0
while runn
romedia on how
they could help this situation, for whatever good that has done. (None,
I suppose.)
Thanks
Mark
-Original Message-
From: Rick Root [mailto:rick.r...@webworksllc.com]
Sent: Wednesday, February 11, 2009 5:57 PM
To: cf-talk
Subject: (ot) More SQL Profiler questions
A
]
Gesendet: Mittwoch, 11. Februar 2009 23:57
An: cf-talk
Betreff: (ot) More SQL Profiler questions
Alright so now that I'm back to using the regular SQL Server JDBC
driver, my queries are flying. Most of them. Problem is, there are
some that don't.
Watching in SQL Provider, all I see is
Alright so now that I'm back to using the regular SQL Server JDBC
driver, my queries are flying. Most of them. Problem is, there are
some that don't.
Watching in SQL Provider, all I see is stuff like this:
exec sp_execute 162, 5909, 1973
That took 956ms of cpu... did over 180,000 reads, and t
9 matches
Mail list logo
