All new features (well, vast majority) work in lower compatibility levels. Compat level just affects how the parser and query processor handle certain T-SQL structures that have changed over the...

I'll give exactly the same answer as last time you asked this question (http://www.sqlservercentral.com/Forums/Topic1501909-1550-1.aspx)

Depends on the type of DBA, the company's needs and roles and the DBA's interests.

Someone who's more...

A picture of the plan is fairly useless. Can you save the plan and attach the resultant file to your post?

I suppose you could insert the results of RESTORE FILELISTONLY into a table run an update to change the file paths, then write a script to generate a RESTORE from...

That's probably what I would have done. Why's it not a valid solution?

Maybe put max server memory back to 14GB and leave it for a while, monitor available MB, watch the ring buffer for memory notifications, watch total and target server memory.

Does SQL need more than it's currently allocating? Is there any indication of internal memory pressure?

Is there free memory for SQL server to allocate?

They don't have a script, they're not T-SQL. They're written in C++ and compiled into dlls which are shipped with SQL Server.

Depends on how much data is going to be affected. It's not fixed. Couple of rows, row locks, fair portion of the table, probably page locks, most of the table,...

Extended stored procedures are written in C++, they do things that T-SQL can't do.

Have a read through this: http://www.sqlservercentral.com/stairway/73776/, especially levels 3, 5 and 7

btw, restore from backup should have been the first thing you tried. Emergency mode repair is the last resort when all else has failed and you have no backup. It...

No. Emergency mode repair failed. That's the absolute final resort, there are no more options left. Restore from your last...

Emergency mode repair is capable of...