Enhance error when connection is broken by a SQL Server issue during import

[PiJoCoder]

Enhancement: When SQL Nexus runs and hits an AV on the SQL Server side, the connection may be broken and SQL Nexus will get this type of error.

ExecuteReader requires an open and available connection. The connection's state is closed

Could there be possible ways to improve the error (bubble some more information from SQL Server up) so that it is clear to the user what happened .

[gambit9009]

When we start looking into this, consider also timeout exceptions. Some SQL Nexus might run a long time and then timeout, probably during the end crunch stages. The data is in the tables. Is there a good/esay way to restart the analysis after import? Is there a better way to catch timeouts, and maybe with a switch or Settings, retry the query that got the timeout? Either by swtich or Settings or with an error messagebox, offer to extend the execution timeout and retry instead of just dying?