arnipetursson (10/23/2014)

---

ScottPletcher (10/22/2014)

---

You should be able to use the session_id to do the lookup. But since session_ids are reused, and sysjobactivity keeps history, if your proc is not currently...

And those same guys obviously did contract work for healthcare.gov! 😀

For temp tables, you must also consider:

INTO #new_temp_table

rather than just CREATE.

Those sound like Oracle qs, but this is a SQL Server forum.

You would likely get much better responses to your q by posting it in an appropriate Oracle forum.

jeff.born (10/22/2014)

---

The solution with the min and max would work if there were only duplicates, but Businesses have been known to be duplicated 100s of times due to previous incorrectly...

SELECT

[BusinessName], [Address], [Phone]

,MIN(Business_pk) AS Business_pk_min,

,MAX(Business_pk) AS Business_pk_max

FROM [dbo].[TestBusiness] bus

INTO [dbo].[DuplicateBusinesses]

GROUP BY

[BusinessName], [Address], [Phone]

HAVING COUNT(*) > 1

You should be able to use the session_id to do the lookup. But since session_ids are reused, and sysjobactivity keeps history, if your proc is not currently running from...

Frank The Tank (10/21/2014)

---

Thanks for all of the responses. Lots of interesting ideas. The computed column approach is probably the most elegant, but it was met with a...

Phil Parkin (10/21/2014)

---

ScottPletcher (10/20/2014)

---

If the controlling column(s) are all from the same table, I suggest a computed column. That leaves the defining logic in only a single place, and...

Increasing the size of a [n]varchar column isn't directly a problem.

But, if you think people will go back and increase the length of those columns in a significant...

If the controlling column(s) are all from the same table, I suggest a computed column. That leaves the defining logic in only a single place, and allows the calc'd...

CELKO (10/20/2014)

---

..SEQUENCEs can "lose" numbers as well: if the transaction rolls back, the acquired sequence number(s) cannot be put back in the pool. If, by law, you can't have...

I prefer EXISTS over NOT IN especially, since NULL values will prevent NOT IN from working. You might see if that also corrects the optimizer issue.

select *

from table_A...

Yes, all modifications to recoverable resources for a single transaction must either all fail or all work, never some and not others. This is fundamental to how SQL Server...

With that many rows, you'll probably want to consider other, more efficient methods of comparing tables.

For example, change tracking would allow you to determine the rows in each table that...