For that database?

What else is in the error log before that Recovering message?

For a DB to be going into recovery often, it would either have autoclose enabled (and hence recovering...

File size and growth changes are immediate, no restarts are needed.

How are you checking the growths and how are you setting them?

Is AutoClose enabled?

If you need to change the default recursion for CTEs, you need to use maxrecursion. Either work with your DBA so that he sees why you need it, or re-design...

Other option for what?

Everyone's an expert. 🙁 http://www.sqlservercentral.com/Forums/Topic1822300-263-1.aspx

Hmm... Odd.

How large are the XML columns being returned by that query? (use the DataLength() function)

Which is what Virtual Chapters do (online meeting software rather than conference calls, but similar enough), and why...

Can you post the execution plan please?

p.s. Are you sure you want the potentially missing and duplicate rows that nolock allows?

Whaaaaaa???

How many sessions involved there?

Yes, you'll be fragmenting the indexes which will require you to rebuild them all (which will grow the file again)

You can reduce the file size, but backups don't contain empty space, so shrinking is not going to reduce your backup size.

You can script the DB, export the data and recreate the DB on SQL 2008, or you can upgrade the 2008 server to 2012, but that's about your only options.

Can't see the size of the VLFs there, but looks like the last one starts just before 500MB and ends, I would guess, at the 534 the log shrunk to....

The first couple of rows of LogInfo is kinda useless when the problem is at the end of the file...

Could be that the VLF sizes are such that it can't...