Timeout duration on linux

Sounds like a timeout setting. So your SSMS thinks it takes too long and cancels the connection for you. The SQL server roles back. But there is help. You are not the first person to encounter this.

See here.

For everybody who doesn't want to click the link. Here is the price winning answer:

After hitting the same error, I stumbled upon the corrent setting.

In the Management Studio, from the Tools menu, select Options, then click "Designers". There is an option called "Override connection string time-out value for table designer updates:" In the "Transaction time-out after:" box, you will see the magic 30 seconds

fping might be a better tool than the stock ping you are using. What OS are you on?

• "fping differs from ping in that you can specify any number of targets on the command line, or specify a file containing the lists of targets to ping."
• "Instead of sending to one target until it times out or replies, fping will send out a ping packet and move on to the next target in a round-robin fashion."
• "Unlike ping, fping is meant to be used in scripts, so its output is designed to be easy to parse."

Example:

fping -c1 -t500 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4

• -c Number of request packets to send to each target.
• -t Initial target timeout in milliseconds