Question: Hello we have an SQL server application running over a low bandwith connection.
We use ADO.NET.

I was wondering if anybody has any tips on minimizing traffic over the channel.
Im looking for answers on ADO.NET/SQL-Server specific tips that make it more efficient.
Not obvious answers like "dont fetch many records". 

En example for MySql would be "enable comptression=true" in the connection string.
I'm cannot find anything on transport layer compression in SQL server.

Do any of you people have experience with this ?
Are there important do's and dont's that we must know ? 

Thanks in advance..

Answer: 
I live in fear of someone doing this to my databases so I always ask my Team to do something like the following:

```
BEGIN TRAN

DELETE FROM X
-- SELECT * FROM X
FROM Table A as X JOIN Table B ON Blah blah blah
WHERE blah blah blah

ROLLBACK TRAN
COMMIT TRAN

```

In this way, if you accidentally hit F5 (done it!) you'll do no changes. You can highlight the SELECT part through the end of the SQL statement to see what records will be changed (and how many). Then, highlight the BEGIN TRAN and entire Delete statement and run it. If you delete the same number of records you expected, highlight the COMMIT TRAN and run it. If anything looks wonky, highlight the ROLLBACK TRAN and run it.

I do this with any UPDATE or DELETE statement. It's saved me a couple times, but it ALWAYS provides peace of mind.
When I want to see what will be deleted, I just change the "delete" statement to a "select \*". I like this better than using a transaction because I don't have to worry about locking.