Posted by Erland Sommarskog on 09/01/07 12:24

(raymond_b_jimenez@yahoo.com) writes:
>> Furthermore, network traffic is not only about bytes, but also about
>> roundtrips. Don't get the details of the order, and then make one
>> call for each product on the order, but get all data at once.
>
> You're absolutely correct! That's why I got another thread going on
> about "SET NO_BROWSETABLE ON". This one seems particularly annoying,
> as it seems it is getting inserted automatically by ADO.Net. Accounts
> for about 20% of the data traffic, and one additional round trip do
> the DB server for each query.

And as I've noted in another thread, SqlClient does not do this when
you use it plainly. Run a plain ExecuteReader or DataAdapter.Fill and
you will not see it. There was a link posted that lead to an article
pointing out the problem with the CommandBuilder.

So that is one more thing to look into. Exactly what in your usage
of ADO .Net (and you still have not told us which data provider you
are using) triggers the usage of SET NO_BROWSETABLE ON.

>> And, yes, while you would have seen a gross cut if TDS was UTF-8 on
>> the wire and not UTF-16, a Chinese user would have seen an increase
>> instead.
>
> Wouldn't it be great to have an option?

If you thinks, submit this suggest on
http://connect.microsoft.com/SqlServer/Feedback.
Personally, I don't think it is worth the pain, also it would also
require changes in the client APIs. And all it would affect is query
batches sent to SQL Server and metadata sent back. If the query batches
sent to SQL Server is killing your network, maybe you should look into
using stored procedures.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]