Sounds like the second table would be joined as a LEFT join, so look up OUTER JOINS in Books Online.

Oh, I agree with Steve here. I'm hating wooden floors more & more with each year. Of course, when we've done demo's and competitions they're sometimes on things worse than...

Weird.

Here's the original link

http://www.alandallessandrokarate.com/%5B/url%5D

Pictures are on the right. I'm the luckless b*****d grabbing the guy from behind.

GilaMonster (12/10/2008)

---

I don't have any photos of what Steve's taking about. I was too busy getting pounded into the mat by Kalen.

I do have a couple of fairly good photos...

Execution plans are your friend.

They will show what the query is doing inside the engine. From there you can determine if you need indexes etc. If the data is not...

You can't get a call-by-call reference, by the dynamic management view sys.dm_exec_query_stats will show you aggregate information about any queries that are still in cache. If they've aged out of...

Is the data loaded through XML being filtered later in the query? If so, use either a permanent table or a temporary table. If not, if the data is doing...

Pull a previous copy out of source control...

If you don't have your code under source control, here's the wake-up call to get it there.

You can't retrieve a previous copy from...

Then supply the correct table name. You should get in the habbit of supplying the schema too, so that it...

That's great. Thanks for following up. It's always good to know what worked and what didn't.

GilaMonster (12/9/2008)

---

Just about every time I've done a presentation or informal training and mentioned the problems...

Sorry for the confusion. Thanks for the clarification Gail.

It's still the approach I'd take, but I'd sure take the time to examine those indexes.

That last query... the uh... you know it... well... uh...

Never mind. That actually makes my current local favorite look intelligent:

DECLARE @i int

SET @i =1

IF @i = 0

BEGIN...

Jeffrey Williams (12/9/2008)

---

Grant, I would not recommend issuing the above - especially since it is deprecated in SQL Server 2008. Here is the message you will get on a...

First things first, I think your statistics may be out of date. on [SWUS].[dbo].[SW_Ord_List_Ext].[_dta_index_SW_Ord_List_Ext_23_254064091__K3_1_4_5_18_20_22] [OLE]. The estimated number of rows is 54, the actual is 48000. That's a bit of...