Every morning during peak hours we get exceptions from our ASP.NET application saying it cannot find a table because the DB doesn't exist, network latency, or because the network name is no longer available.
While we're looking into other possible reasons for this, we wanted to know if there are any SQL server diagnostics that you can suggest. I tried running sp_lock and sp_who2, but it only shows LIVE information. The problem is that the exceptions only last for a very short period of time.
So what I'm looking for is something like sp_lock & sp_who2, something similar that I can just leave running or something. Then when I get email notifications that exceptions are happening, I can go and look at diagnostical data produced.