Correlated subqueries are not necessarily executed once per row of the outer query (which I assume is where the 'like loops' came from), the one in this query certainly isn't....

SQL will grow one then the other, that's why you see them both growing. They're still used sequentially, the log reader reads sequentially (by LSN), all writes are sequential. There's...

http://www.microsoft.com/learning/en/us/certification/cert-sql-server.aspx

No it's not. If you were talking about a nonclustered index, that would be the case, but...

The table...

Parametrisation is not required for plan reuse. Parametrisation results in better reuse of cached plans, it's not a requirement for any having any reuse at all.

SQLSACT (12/11/2012)

---

sp_executesql is gonna use a plan that is already in the plan cache, whereas executing the batch on it's own is gonna generate an execution plan, unless you're using...

I strongly recommend you do not go this approach of generic delete procedures.

No. You're not looking for login information, you're looking for database access information. If you were...

That's the best you can do without custom auditing. The information you want is not kept by SQL by default.

CTP - Community technology preview. A pre-release version of SQL 2012 for testing. You don't want those, they're not full versions and they've all likely expired at this point.

If you...

Compare duration, CPU and reads as well as the consistency of the performance.

Firstly, turn traceflag 1204 off. It produces the old-style deadlock graph that's very hard to read. With just 1222 on, wait until another deadlock occurs and post the entire deadlock...

No. There's 2 in the UK that I know of, hence,...

When working with large tables:

Retrieve just the data that you absolutely need.

Understand that no one is going to read several million rows, hence do not query several million...