I'm glad you got it figured out!

The LOG_BACKUP reuse wait description indicates that space in the log could not be reused because a log backup had not occurred since the...

Ah, my apologies, I fear my explanation was not clear enough.

How much memory to add is exactly what you have at the end of the process I described.

I'm not...

I know you say it's grown very big, but is the size of the file actually causing any problems?

If it is causing actual problems (for example, it's running the...

Well, a couple things bear mentioning.

First, switching the recovery model from Full to Simple, shrinking, and switching back to full is a terrible trick for shrinking the log file, not...

This is actually something I do on a regular basis in evaluating environments, and the following is the method I've settled on.

I first check PLE during during business hours, and...

Alas...well, as you say, it was worth a try.

That is indeed quite puzzling. At the moment I don't really have any more ideas.

I'm actually beginning to think that my whole...

Ah, I was hoping it would be more helpful. C'est la vie.

At one visible core I wouldn't expect there to be any balancing issues.

If you run the query with OPTION...

I assume you're referring to the ungodly-high Anything/sec counters?

It should seem extraordinary, and you're not crazy 🙂

Those metrics, despite being named .../sec, are not actually stored as a per second...

Have a look at these two articles, particularly the latter:

http://sqlblog.com/blogs/aaron_bertrand/archive/2012/04/27/a-cautionary-tale-about-grandfathering-CAL-licenses-in-SQL-Server-2012-Enterprise.aspx

http://sqlperformance.com/2012/11/system-configuration/2012-cal-problems

In your case, the imbalance from doing round-robin between a socket using 12 cores and a socket that only has 8...

Yeah, to expand on what djj said, the trick is that those two columns are a composite key in the clustered index, and the order of the columns makes a...

This basically means that you've filled your transaction log file and it cannot grow, either because autogrowth is disabled or it's reached its maxsize.

There are a few things I'd look...

Lynn's seeming remembrance is spot-on. 🙂

A nice read on temporary object caching and what does/does not prevent it can be found here: http://sqlblog.com/blogs/paul_white/archive/2012/08/17/temporary-object-caching-explained.aspx

Cheers!

Is there any way you could get the actual execution plans for both queries as .sqlplan files and post those?

That would give us a bit more detail to work...

You're on the right track.

Both processes have requested locks on both pages, but in different orders.

The SELECT first requested an S lock on page 10088721, and that request was granted.

Meanwhile,...

Something like the following would construct the EXEC command dynamically:

DECLARE @db VARCHAR(250)

SET @db='Some Database'

DECLARE @sql VARCHAR(1000)

SET @sql='EXECUTE '+QUOTENAME(@db)+'.[dbo].[sp_fulltext_database] @action=''enable'''

EXEC (@sql)

I'm curious, though. What exactly are you...