Very interesting. It doesn't do that on mine but apparently it is supposed to be the default behavior.

http://technet.microsoft.com/en-us/library/cc646024.aspx

When debugging transact-sql statements it stops by default on the first line...

Lynn Pettis (4/14/2010)

---

And I did. Just waiting now to...

Typo

There should have been no need to hit continue on the query.

EDIT: fixed typo.

It looks like you can come back now.

Did you add any breakpoints?

Mister Ken (4/14/2010)

---

I saw a coworker's snippet once, it reminded me vaguely of a similar idea. The statement below works.

UPDATEt1

SET t1.ID = NULL

FROM dbo.table1 t1

WHERE EXISTS(SELECT * FROM #table2 t2...

The external column throws an error every which way you try to configure it. My answer on...

Have you checked statistics, execution plans, indexes? Have you checked for blocking? Do you have any traces running?

Please provide the query and actual execution plan - better answers...

I missed it as well until I copied it ans pasted to my query window - then it became obvious.

Also, I was surprised to see the sudden responses all while...

The initial query would provide an error.

That looks similar to what we are using. Meaning - we use the same kind of setup but different accounts obviously.

Mister Ken (4/14/2010)

---

Actually there was a small typo to the select statement.

select #table1.field1, lookup.line_count

from #table1

inner join (

select field1, count(*) line_count from #table2 where field2 > #table1.field2 group by field1

) lookup

on...

select t1.field1, lkp.line_count

from #table1 t1

inner join (

select t2.field1, count(*) line_count

from #table2 t2

Inner Join #table1 tt

On tt.field1 = t2.field1

where t2.field2 > tt.field2

group by t2.field1

) lkp

on t1.field1 = lkp.field1

I believe...

You're welcome.