Also, here is a snippet of code that you might be able to use to avoid PK violations:INSERT

DataIntegrityErrors

(

...

Is the problem that there are two (or more) rows being generated with duplicate primary keys by your query or that the primary key already exists in the destination table...

Given your source data when you pass a 2, what do you want as output?

Just as an FYI, I did get the following query to work. However, I do not think I'd trust it to ALWAYS work in production:SELECT *

FROM

(

...

Actually, I was just looking at some old code and apparently SQL is "smart" enough to figure out what is going on so it will, in essence, collapse the query...

RBarryYoung (7/13/2009)

---

To the best of my recollection, you canNOT normally create FK constraints for self-referencing relations, because sometimes the ParentID has to be NULL which cannot effectively be handled by...

I was doing a quick scan, so hopefully I did not miss it, but did you try a derived table yet?

There is probably a more elegant solution, but this handles strings of 15 characters and such:DECLARE @Foo TABLE (Val VARCHAR(50))

INSERT @Foo

SELECT 'michael the greatest thing ever!!'

UNION...

Something like:DATEDIFF

(

HOUR,

cast(stuff(stuff(stuff(cast(SAP_CRM_P1_Calls.ED_TST_TO as varchar(17)), 9, 0, ' '), 12, 0, ':'), 15, 0, ':') as datetime),

SAP_CRM_P1_Calls.[Downtime Start]

) AS [Service Order Duration (hours)]

Nice article. I've used other commercial geo-location products in the past and it is nice to have a free solution that is able to get reasonable results for BI tasks...

Whitefang, is that you?

Casting to an INT should work just fine. However, you *might* be able to get a slight performance increase by eliminating a function on one the join values and just...

Carl is correct about tracking changes from Server to Server and database to database. However, if you wanted to track changes within a given database you could, but you would...

WayneS (7/7/2009)

---

Here you go.

Note that you don't actually have a NULL value in Field2; instead you have the string "NULL'. The code handles this.

-- with this clustered index, the following...

There are much nicer solutions (if you have SQL 2005 or later), but here is one way to do it:DECLARE @test-2 TABLE (

[ID] [int] NOT NULL,

[Field1] [nvarchar](255) NULL,

[Field2]...