SQL Nexus may spend a long time processing, get timeout exception and close.

[gambit9009]

Some SQL Nexus might run a long time and then timeout, probably during the end crunch stages. The data is in the tables...already imported.
Is there a good/easy 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 switch or Settings or with an error messagebox, offer to extend the execution timeout and retry instead of just dying?

Spinning this off of #143.