We have tried using a different MS SQL JDBC driver -- outside of the
standard Macromedia SQL Server JDBC and CFMX runs "really hard" in
comparison. Our average running requests are 2ish running request/sec
and when we change to a different jdbc driver we run about 7-8
requests/sec becuase the requests are backed up since it takes CFMX
longer to respond. The driver does work but becuase it takes longer we
end up maxing out the server very quickly. We are running CFMX
Enterprise on win2k boxes.
Is there some "flag" in an xml file that we are missing or some other
attribute? All that we are doing is selecting "other" for the
datasource in the administrator and filling in the correct driver
details. Why are we trying to use a different driver -- more longing to
identify trouble areas in our code.
Thanks,
Jeremy
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
