Hi,

I've got a question on the best way to handle the DB going offline. I have a windows service, which has a number off threads actively interacting with the DB (SQL Server). I guess I'm thinking ahead of the actual problem - but what is the best way to deal with DB going offline in NHibernate? Are there any best practices or recommended approaches?

Using a try-catch approach inside of an infinite loop approach (it is highly unlikely the DB will be down for longer than 2-3 minuts) seems excessive (one way that i though of dealing with the issue)...

Any comments and recomendation will be much appreciated.

Thanks in advance,
Nick Goloborodko

As far as I am aware, the only recommendation NHibernate has regarding exception handling is described here:
http://www.hibernate.org/hib_docs/nhibe ... exceptions

The nature of most windows services is that they do the same thing over and over again. Therefore, running some form of an infinite loop is not unreasonable. Of course, you don't want to be hitting your database every millisecond. Depending on your need, I found that using a timer works for me. A few of my applications hit the database every few minutes to see if there is any work to do; if so, do it; if not, sleep and wait. If the database is not there... well, sleep and wait anyway.

Hope this helps.