Right, and thanks for the response btw. The main trouble is that we could not afford the time to be checking through and changing all the possibly affected queries in our rather sprawling legacy application (getting less sprawled by the day) - the jTDC driver gives us the needed performance improvement without having to touch our code. It wouldn't seem right either, given that the SQL syntax was correct, to be editing all those queries to work with the MS driver.
Dominic On 1 February 2010 14:27, Leigh _ <[email protected]> wrote: > > >It appears to be a limitation of the M$ jdbc driver. > > I do not know that it is a limitation of the driver. From everything I > have read, I have always felt it was due to CF's handling of multiple > statements within cfquery, and the whole one query/resultset limitation. > Though I prefer procedures, I have definitely used multiple statements > within cfquery + the MS driver in the past (usually with SET NOCOUNT ON/OFF) > . > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:330296 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
