|
|
Posted by Erland Sommarskog on 09/01/07 15:04
Erland Sommarskog (esquel@sommarskog.se) writes:
> (raymond_b_jimenez@yahoo.com) writes:
>>> 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.
Thinking of it, rather than having to select the character encoding, it's
better if the option was for compression of the network traffic in general.
But I find it difficult to believe that this would be a good option
for the traffic between a web server and an SQL Server that are on
the same LAN. It could possibly be an option if you are on a slow connection
over VPN. In general, I have a feeling that the network considerations
for SQL Server are for LAN connections, because that is surely the most
common scenario.
--
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
Navigation:
[Reply to this message]
|