Grant Fritchey (12/31/2008)

---

Even though SQL Server 2005/2008 will store excess values past the 8060 limit when dealing with varchar,etc., you will get performance overhead to go and do that extra...

And Jeff's post is better formatted also 😛

Jeff Moden (12/30/2008)

---

Jeffrey meant that if you give room for a mistake to happen, it will happen. You shouldn't make VARCHAR any bigger than necessary or you stand a...

klini (12/30/2008)

---

Thanks.

I've meticulously tried to get my varchars to match what I expect the data to look like. I'll now just set everything to 8000 and save myself a...

Also don't forget that if you have other columns or...

OK, now I'm slightly confused. It actually looks like the TOP 1 in the IN statement does make a difference!

Check out the execution plan:

SELECT o.SomeInt

FROM #MyInTable AS o

WHERE o.SomeInt in

(

SELECT...

It's interesting looking at the execution plans for the two queries:

SELECT o.SomeInt

FROM #MyInTable AS o

WHERE o.SomeInt in

(

SELECT top 1 p.SomeInt FROM JBMTest AS p

WHERE p.SomeInt = o.SomeInt

)

|--Nested Loops(Left...

RBarryYoung (12/30/2008)

---

One thing that I noticed is that you have reversed the roles of the tables in Jeff's example. Originally, Jeff had #MyInTable as the subordinate table, but you...

Fixed... sorry about that.

I'll post some observations tomorrow.

Ummmm... apologies, it seems I've accidently widened the page 🙁

Anyone know how to fix the post?

Well here is something interesting. Unfortunately, I'm still learning about the underlying database engine (I'm only half way through Karen Delaney's excellent Query Tuning and Optimization book for SQL Server...

Hmmmm... I think I'm going to definitely test this one out myself!

When I do I'll post my results.

lol, it was 🙂 Definitely brought a smile to my face. And I got 8 points...

Oh man... I thought that a PUN was the lowest form of humour. Guess I was wrong 😀

Good point. I concede the point!

Question was badly asked.