A Transport-level error

Question

Our .net application throws an error when the wireless laptop switches from wireless access point to another inside a building. it seems like SQL is closing the existing connetion without notifying the application which thinks that sqlconnetion is still
in OPEN state. why does SQL close a connection without notifying the application? Our programming team does not want to open and close the connection on each transaction because they think it will slow down the application.
Error:
"A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"

Answer 1

I would expect a disconnect error in such a case.
I don't think SQL Server has a design feature to follow mobile wireless devices.
Threads:
Timeout issue when connection to SQL Server in Wireless environment
Having disconnections with SQL Server using a wireless connection
QUOTE: "Ah, SQL Server connections (and the connection pooling mechanism) are not at
all tolerant of WiFi connections. I suggest you use a replication technology
as exposed by the SQL "Server" Compact Edition and ADO.NET 3.5 Sync
Services. This gives you a local DBMS to work with and connectivity designed
to work over an occasionally (and unreliable) connection."
You may try to adjust the TCP/IP Keep Alive parameter, but no guarantee though.
BOL: "Keep Alive
This parameter (in milliseconds) controls how often TCP attempts to verify that an idle connection is still intact by sending a
KEEPALIVE packet. The default is 30000 milliseconds."
LINK:
http://technet.microsoft.com/en-us/library/ms190771(v=sql.105).aspx
Related thread:
Wireless connections to SQL Databases
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012