Controls how many statements are sent to the server in a batch.

The actual batch is broken up into pieces this large that are sent separately.

Currently j TDS automatically falls back from 8.0 to 7.0 (if used with SQL Server 7.0) and from 5.0 to 4.2 (with Sybase 10) so specifying the value for this parameter is only necessary for SQL Server 6.5.

The JNet Direct license precludes publication of performance test results.

However, you can run any of the benchmarks yourself, the effort is minimal.

Once the timeout value is exceeded the network or named pipe connection will be closed.

This parameter may be useful for detecting dead network connections in a pooled environment. TDS (Tabular Data Stream) is the protocol used by Microsoft SQL Server and Sybase to communicate with database clients. Version 4.2 is used by SQL Server 6.5 and Sybase 10. Version 7.0 is used by SQL Server 7.0; this protocol also works with SQL Server 2000.

The reason for this is to avoid Sybase "hangs" caused by running out of space with very large batches.

The problem doesn't seem to occur with SQL Server, hence the default limit of 0 (unlimited) in this case.There is a performance hit for the encoding logic so set this option to false if unitext or univarchar data types are not in use or if charset is utf-8.The amount of time to wait (in seconds) for a server response before timing out. If a non zero value is supplied this must be greater than the maximum time that the server will take to answer any query.So when using multiple Controls whether the j CIFS library will be used instead of the local file system with named pipe connections on the Windows operating system.(The j CIFS library will always be used with named pipes when the operating system is not Windows.) Useful when connecting via named pipes to a server that is located in a different domain than the client. Actually we do have benchmark results from two different benchmarks, both developed by large commercial SQL Server JDBC driver vendors to demonstrate the performance of their own drivers.See also use experimental true distributed transaction support. ^ top ^ j TDS is supposed to be the fastest JDBC driver around. In our oppinion this is better than having a benchmark of our own, which could be designed in such a way as to give j TDS the edge.