Just FYI: KEEP PLAN just changes the recompilation threshold for temporary tables to match the...

Congrats!

That's a pretty straggly-looking deer 😛

Hi Tom,

The third question in this series will be published next week (8 September).

I promise your question will be answered then.

Paul

Nils Gustav Stråbø (9/1/2011)

---

A similar example is how the INNER JOIN is removed (resulting in only a scan on table "child") in the following example, due to the fact that...

I couldn't include a graphic in the answer, so here's the query and execution plan:

DECLARE @A TABLE (a INT NOT NULL UNIQUE)

DECLARE @b-2 TABLE (b INT NOT NULL)

SELECT COUNT_BIG(*)

FROM...

Agreed, but I had to...

Nice easy one today. I wonder how many will get it wrong though?

Just for the record:

Well the bug response from MSFT was unexpected:

"Since this is not a common scenario or use case i.e., doing DDL changes and DML in the same transaction we don't see...

Gah.

I signed up as a member when the site first got going and I wanted to leave...

GilaMonster (8/26/2011)

---

That did occur to me, and that table does not (I believe) have a primary key (unless someone made it nonclustered), his comments seemed to suggest that the rows...

I once worked at a place where a lack-of-WHERE-clause-highlighting issue produced the mandate that everyone should connect with IMPLICIT_TRANSACTIONS ON. It can be a bit of a PITA sometimes...

Without clicking the link (I should know better!) one way is...

I added a quick Connect item for this bug, to let the powers that be know. I'll happily remove it if and when Jack enters one.

https://connect.microsoft.com/SQLServer/feedback/details/685800/parameterized-delete-and-merge-allow-foreign-key-constraint-violations