We are migrating an DB2 database to sql server 2005. We have used the 1.2 jdbc driver. It consumes lots of memory when we have several resultssets opened on different statments. Then we tried JTDS (http://jtds.sourceforge.net/), it worked fine. It's supports concurrent staments. We would like to stick with microsofts driver. My question is: will we se this supported in microsofts driver (soon)!
Joachim
Hi,
By any chance, are you setting the "responseBuffering" property to "adaptive"?
To keep back compatibility with our v1.1 driver behavior, our default behavior is to cache the entire resultset. So, in your scenario where you have multiple resultsets open at the same time, the driver will consume a lot of memory.
With responseBuffering=adaptive enabled, the driver will only consume as much memory as needed to retrieve the immediate data from the wire. Specifically, for CLOB and BLOB are streamed unless marked by the application.
I love to hear back if responseBuffering=adaptive resolves your scenario.
Jimmy
|||Hi!Setting the property responseBuffering=adaptive did not help. When the first statment is opened, there is no increase in memory usage. As soon as we opens the next resultset the memory usage start to increase rapidly. When we use the jdts driver this does not happend. As i wrote before, we would like to use the microsoft driver (its the corporate strategy).
But we need to see the memory handling as in jdts.
Thanks for your rapid replay.
Joachim
No comments:
Post a Comment