"Bojidar Alexandrov" <bojo_do_not_spam@kodar.net> wrote in message
news:OjD#rHy6DHA.2472@TK2MSFTNGP10.phx.gbl...

> I have next question - What are best practices to catch situation when
there
> is a loss of connection between application and SQL Server for few
seconds?
>
> As I have found till now in Internet - Connection.State is not affected by
> loss of connection - it represents state after last executed command and
> best is to catch this in error handler.
> What types of errors I must catch? Is this reliable?
> How to determine if query need to be executed again? For example -
executing
> of stored procedure that perfform some modification of data an return
status
> after that. If application never receive this because of network eror what
> to do?

> <Warning: Slightly off topic answer here :>
> One thing you may want to check, if you've got database
autogrow/autoshrink
> enabled, I've seen applications loose connection while the database is
> adding additional file space.
>
> To get to the bottom of a network disconnect I'd suggest running a network
> monitor trace.
>