With firehose cursors the SELECT query is sent and the server responds with all the resulting rows.
This is the fastest approach but it means that the driver has to cache all results if another request needs to be made before all rows have been processed.
The MAC address cannot be determined automatically from Java (i.e.
without using native code) so you'll have to specify it yourself if you need it.) will enable fast caching (uses less memory and has no overhead associated with removing statements); the cache will never release any cached statements, so although experience has shown that this is usually not a problem with most applications, use with care. When the SQL Server and the client are on the same machine, a named pipe will usually have better performance than TCP/IP sockets since the network layer is eliminated. JCIFS provides a pure Java named pipe implementation and uses NTLM authentication, so the Determines whether string parameters are sent to the SQL Server database in Unicode or in the default character encoding of the database.
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.
True distributed transaction support is only available for SQL Server 2000 and requires the installation of an external stored procedure in the target server (see the README. These benchmarks are free to download so we encourage you to do it and run them yourself.
This seriously affects SQL Server 2000 performance since it does not automatically cast the types (as 7.0 does), meaning that if a index column is Unicode and the string is submitted using the default character encoding (or the other way around) SQLServer will perform an index scan instead of an index seek.
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.
We have benchmarked j TDS against the two most used commercial drivers and of course the Microsoft driver and the JDBC-ODBC bridge, using these benchmarks: i-net software's Bench Test 2.1 for MS SQL Server and JNet Direct's JDBC Performance Benchmark.
Here are the results of the i-net test: Bench Test 2.1 for MS SQL Server.
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.