>>If I'm looking for reliability I have connections open only the bare minimum amount of time needed to communicate with the backend. It used to be expensive to frequently connect and disconnect like that, but my understanding is modern versions of RDBMSs cache or pool connections so there's not much impact.
>
>Yes, this is what I recommanded. But, I was just trying to see if this is a normal behavoir that it reacts like that.
The client-side software (Native Client, ODBC driver etc.) you're using to connect to the backend is its own process, it's not part of your app. As such it can do its own connection monitoring, pop up error messages or anything else it wants to do.
It looks like in some cases it's possible to instruct the client-side software what to do in case of errors e.g.
http://technet.microsoft.com/en-us/library/hh213129.aspxIf you're going to wrap your queries in open/close wrappers then this all becomes moot anyways.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
