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 took nearly 10 seconds to run. And I have NO idea what the query is or how to find out what it was. I wasn't running the trace when the statement was prepared so all I know is that the "ID" of the prepared statement is "162" Anyone dealt with this before? -- Rick Root New Brian Vander Ark Album, songs in the music player and cool behind the scenes video at www.myspace.com/brianvanderark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:319198 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
