There is a difference between simply including a column and adding it to the index. You add a column to the index because it is part of sorts, searches, joins,...

No, not a simple equi-join, no. A simple outer join, yep.

http://www.sqlservercentral.com/articles/Advanced+Querying/outerjoinmystery/2382/

Can anyone show me a single instance of any individual walking through 1m records one at a time? Every time I've been given the requirement "we need to see all...

Maybe I'm confused, but you can't browse the transaction logs. The error logs, which you can browse, aren't going to show much from "activity" but rather from logged events, errors...

antony (10/15/2007)

---

Hi,

You can update you query in best way like below

Update TableA set a.col3=b.colc,a.col4=ColD,a.col5=ColE from TableA a, TableB b

Where b.ColA = a.Col1

Its similar like the join Query. Try This...

In the interest of completion. Here's the execution plan for the latest solution. I'd stick with the simple join statements:

Actually, I can add one more bit of info:

http://www.simple-talk.com/sql/performance/sql-server-performance-crib-sheet/

Jeff Moden (10/14/2007)

---

"This is the hammer that, I suspect, will be used to hammer in nails, screws, and 2x4s in projects [...] It will be overused. Don't let your...

Jeff Moden (10/13/2007)

---

Grant, I'm with you... I see no compelling reason for CLR's. My opinion, for the most part, for them being there is the same as DTS and...

No, we're not searching against it. We simply return it as XML. I have looked into using the XML indexes, but that nine times data storage that I keep reading...

We are using it in some places. The purpose is pretty much self-explanatory, we want to persist XML data and having an XML data type for storage ensures that we're...

I can't replicate the behavior. I tried using trusted connections & sql connections and unchecking the "remember password" on the connection window. Once I'm connected to a server, every time...

Correct me if I'm wrong, but doesn't the black box trace only keep a rolling set of data? You'll need to set up an actual trace. Make it to file...

I have to agree. The inner join seems like the most logical approach.

Using the same temp tables above:

UPDATE #TableA

SET Col3 = b.ColC ,

Col4 = b.ColD,

Col5 = b.ColE

FROM #TableA a

INNER JOIN...

I'm not sure I have the precise answer, but I was just reading how certain errors can't be trapped at the moment of execution, but can be at a level...