Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Java
jTDS driver
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="JScoobyCed, post: 613567"] Thanks all for your advices. Again, I know that a good DB layer on the application and a good DB design are the major factors to efficient DB access. We are working on this. We did already pool the connections, we had also our transactions as short as possible to prevent blocking other users. Still we have some design issue, indexes to add, queries to re-write. We are almost done. I thought my question was simple: is there any settings that would make a difference between MS SQL drivers and jTDS (that means the processing time spent in the driver classes, provided our application refactoring/redesign is completed and optimal) ? From Thomas answer, it looks like I have been misleaded to this driver, as no real difference seems visible. We did benchmark both drivers in the same environment/conditions, without significant results (not yet with our new architecture, it's coming :) ). Thus my question of any specific settings/design to really use the power of jTDS. Now, I guess I shouldn't spend too much time on this as it appears that this driver won't help us much. I will come back to the suggested database newsgroup when we are ready to benchmark again. Thanks again. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Java
jTDS driver
Top