I have a dev environment that is rapidly approaching deployment into production and have noticed in the logs that roughly every 20 seconds I see the message:
Starting up database 'dbname' CHECKDB for database 'dbname' finished without errors
I noticed this because the end users who are testing this had a problem which I isolated to an error that I noticed in the Windows Event Log (Application Log):
The log for database 'dbname' is not available. Check event log for related messages.
Incidentally, I found no related messages but resolved with offline/online cycle.
The only thing I can think of is that this application collects data every 1ms, but all of this data does not get inserted into the database. Being a dev server, it was config'd so that logs and data are on the same drive. With these two pieces of information in mind, I'm leaning toward this being an IO issue and that the server is attempting to recover from a loss of connection to its storage (SAN). Yet even this doesn't make sense to me because it is not losing all dbs, just this one. What else could be causing this?
Platform: SQL Server 2008 R2 (Ent.) on Windows Server 2008 R2 (Std.)