Ah i see. Yeah mine wont work. Think i would go for something like your second post then. Not much choice as i see it.

/T

steven.malone (12/8/2010)

---

Caution:

Any null values returned by subquery or expression that are compared to test_expression using IN or NOT IN return UNKNOWN. Using null values in together with IN or...

Richard McSharry (12/7/2010)

---

Let's say you have range called Tundra, and that range has 3 weights: 40oz, 50oz, 60oz.

Let's say that Tundra comes in 40 different colours and all colours are...

jaganmohan.rao (12/7/2010)

---

Good question! But missed the Batch Separator(GO(default) or 😉 between the Insert statements.

INSERT INTO dbo.Employees(EmployeeID) values (1)

GO

INSERT INTO dbo.Employees(EmployeeID) values (2)

GO

INSERT INTO dbo.Employees(EmployeeID) values (3)

GO

INSERT INTO dbo.Employees(EmployeeID) values...

Hardy21 (12/7/2010)

---

ziangij (12/6/2010)

---

Is the same number (16) applicable for a clustered index in SQL Server 2008 ?

Checked the link, could not find if the above number is different in case...

ziangij (12/6/2010)

---

Is the same number (16) applicable for a clustered index in SQL Server 2008 ?

Checked the link, could not find if the above number is different in case of...

Nice article as a whole... a bit weak/confusing intro though. But thx to Craigs little comment it became much more clear what/why was being done.

/T

roger.plowman (12/2/2010)

---

I had the need for this and used a non-clustered unique filtered index. Simple, efficient, and solves the problem neatly while letting SQL Server enforce it.

As to why you'd...

Is that really slow? If its between servers on a network then thats not so bad. I just did a simple copy over my network on a 2GB file and...

There are several threads about this in these forums. Search is your friend 🙂

This is

http://www.sqlservercentral.com/Forums/Topic943562-338-1.aspx#bm944589 is according to most one of the better ways to do it.

/T

Not going into whats better or worse. But your SET based version feels... overkill.

update x set UpdatedValue = UpdatedValue * IsNull(Factor, 1)

from @x x

cross apply (select EXP(SUM(LOG(DilutionFactor))) Factor

...

There is no **** way that "By adding a where clause in ALL inserts that checks for the existence of new value in the table" is a fix to a...

Problem with @@error is that it catches the LAST error. So say you execute 3 deletes and the first fails. If you after the deletes check @@error its going to...

Okay im sure im totally missing something here but adding either

ORDER BY Convert(integer, number)

or

ORDER BY Len(Number) ...

The second select have a LEFT JOIN as well. So even though there is no match you still get the row. Hence the 'S' row.

/T