In all my years of working with Sql Server and the SSMS I've never seen a database listed as "In Recovery". Since installing SQL Source Control a week or so ago, I've now seen it twice.
"In Recovery" appears to be a mode that SQL Server puts a database catalog into when it was incorrectly shut down due to, say, a sudden power loss. The ACID nature of Sql Server guarantees that transactions either wholly succeed or wholly fail. So if the server crashes during a transaction, it is necessary on starting it back up to either complete or roll back any transactions that were previously in operation. It's fairly amazing how durable (the D in ACID) this process is.
So far, I don't see any corruption of my small test database as a result of this, but I am concerned at the thought that SQL Source Control could somehow trigger this. Has anyone else experienced this before?
Some particulars of my situation. I am running a MacBook Pro with Parallels, a virtual machine program hosting a Windows 7 Home Premium VM, on which I'm running SQL Server Express 2008 and SQL Server Management Studio 2008. This most recent time I did a full, ordinary shut-down of my VM Friday and Monday morning did a regular start-up, manually starting the SQL Server service manually and launching into SSMS moments later. There is no other program connecting to this instance of SQL Server currently. And there is only one (user) catalog installed on it for now.