Me talking to my developers: “Well, guys, I’ve got good news and bad news. Bad news first: looks like somebody forgot about today’s scheduled outage, and they were trying to load data when the network admins shut down the database server. The ETL database is now trying to recover the messy transactions, and the server could be down for a few hours.”
“The good news, though, is check out the cool new SQL Server 2005 icon for databases that are in recovery mode! Is that cool or what?”
How do you fix this? I have an Adventure Works db on a dev server that seems to be stuck in this loop
Brent – if it’s AdventureWorks, the sample database, and you’re sure you don’t need any content out of it, I’d delete the AdventureWorks files when the SQL Server service is stopped.