Possible to compress SQL Server network traffic?

Question

I have a .NET client that needs to connect to a remote SQL Server over the WAN, is it possible to compress SQL traffic between the client and the server?

I am using .NET 3.5 and SQL Server 2005 and greater.

Answer 1

Check this out : http://www.toonel.net/tcpany.htm

Btw, I also think that SQL Server itself cannot compress trafic, but, with a network tier within application - you can do the compression there.

Answer 2

I know this question is over a year old but I found myself looking for this so I thought I would share what I found. There is this (quite expensive) software that compresses SQL server traffic. I am testing it at the moment for one of my clients, it works very well, achieving 60% compression ratios on average.

http://www.nitrosphere.net/store/nitroaccelerator

It is also compatible with clients that don't have this service installed.

Answer 3

if you want to create a tunnel with compression and encryption (can be disabled to save process) without having to create a vpn and also is cross plataform for your delight, here you have one that functions as a client server and using listening ports all life also functions as a firewall as a tunnel to have a single port as a channel to manage remote connections and ports), this tools exists 10 years ago: http://www.winton.org.uk/zebedee/

I'm doing experiments to compress (at level 3) a connection unencrypted SQL Server and I 'm getting good ratios tuneando the level of compression, let the intention that children spend large queries possible data for the limited channel... updated in: https://sourceforge.net/projects/zebedee/

Answer 4

We are currently also testing the NitroSphere software over our WAN network, and we have a 73% compression rate, and a big speed improvement.

My opinion is that the software is actually cheap compared to SQL Server licensing, Riverbed devices and MPLS WAN connections. So for sure have a look if you have bandwidth troubles. It also support encryption but we do not plan on using this since everything will stay on internal MPLS network.

Answer 5

Looking at the connectionstrings.com here for SQL Server 2008, the database providers do not have some kind of compression scheme...You may need to write a wrapper on a different port, that compresses the data, by using the front end, send the data across that port, from there, compress it, send it across to the remote endpoint, decompress it, and forward it on to the real tcp/ip port where the server is sitting on.

Usually SQL Server sits on port 1433...

Since a picture is worth a thousand words....

+--------+                                             +--------+
| CLIENT |                                             | SERVER |
+--------+                                             +--------+
  Port 1234                                          Port 1433 <+--+
     |                                                             |
     |                                                             |
     +={Module}=    <=>    TX/RX    <=>   ={Module}=  -+-----------+

The module will sit there on both ends compressing/decompressing...

To be quite honest, it sounds like there will be work involved as the Firewall's holes would have to be punctured to allow the compressed data in and out...throw in NAT/SNAT could make things complicated...

Have a look at this article that I wrote on Codeproject, that code acts as a traffic redirector and could easily be modified to use the compression/decompression scheme..

Answer 6

In this case I suggest to use web services or WCF to send the data instead of using connection to the database.