Stephanie Giovannini (6/26/2008)

---

I always remember that unique constraints allow nulls, but forget that they only allow one null (assuming the constraint is on just one column).

I have a table in...

Matt Miller (6/26/2008)

---

Hmm... sounds to me that you have a much bigger issue than a design disagreement.

A natural key that will end up with duplicates is no longer a...

Also be aware that neither of those will handle the TEXT datatype. What you might want to look into is the undocumented sp_execresultset...

If you're using SQL Server 2005, lemme...

The real problem is that you're using the same table for OLTP and Batch processing. Load the data into a separate table (staging table), process it, the transfer the...

To wit...

http://www.sqlservercentral.com/articles/T-SQL/63003/

Jeff Moden (6/26/2008)

---

Michael Earl (6/26/2008)

---

You can use *= and =* for outer joins when putting joins in the WHERE clause. This is the old ANSI standard for join syntax....

Michael Earl (6/26/2008)

---

You can use *= and =* for outer joins when putting joins in the WHERE clause. This is the old ANSI standard for join syntax. Using...

GSquared (6/26/2008)

---

You can always build a set of left outer joins between the two tables. That'll give you which exact column was modified.

Something like:

select t1.Col1

from dbo.Table1 t1

left outer join...

That's what the OP is trying to avoid, Gus... OP wants the temp table to size itself and it's columns like it would using a SELECT/INTO except the OP wants...

schuppe (6/26/2008)

---

create table testtable (startdate datetime, enddate datetime)

insert into testtable values(getdate(), dateadd(day, 5, getdate()));

with test (startdate, enddate) as

(select startdate, enddate from testtable

union all

select dateadd(day, 1, test.startdate), test.enddate...

Michael Earl (6/26/2008)

---

Search for "Tally Table" on this site and you will find some articles by Jeff about how to do this. He's a pretty smart guy and his...

GSquared (6/26/2008)

---

For 2000, take a look at Jeff Moden's Running Totals article on this site. You should be able to use a variation on that. Bit more complex...

In that same vein...

DROP TABLE JBMTest

GO

--===== Create and populate a 1,000,000 row test table.

-- Column "RowNum" has a range of 1 to 1,000,000 unique numbers

...

First, the warning about nulls is just that... a warning to let you know that some rows had nulls and they were ignored. You can suppress that message with...

Heh... rowcount can be wrong in sysindexes unless you run the correct DBCC command to update them... that's a hint... look it up in Books Online.