Only 'YYYYMMDD', rather than 'YYYY-MM-DD', is 100% safe:

INSERT INTO T1 (createdate)

VALUES ('20120309 12:34:45:567')

I'd suggesting not using that particular new "enhancement" at all while you still have ANY older instances / compatability settings.

It doesn't save you that much anyway. Not worth the...

Whenever possible, you should use:

EXEC sp_executesql @sql [rather than EXEC(@sql)]

because it is far less susceptible to SQL injection, although not foolproof depending on what...

Here's another possible approach, in case you ever have to do (many) more columns 🙂 :

DELETE FROM dbo.trefClientShares

WHERE

CASE WHEN intLMid IS NULL THEN 1 ELSE 0...

Based on Dr Codd's rule, ALL existing relational DBMSs are "fundamentally wrong". NONE of them come close to implementing even the initial 12 "rules".

So, if we all behaved as...

CELKO (12/11/2012)

---

In COBOL, the display and the internal format of data was the same. Each field had a PICTURE clause to define it. Your question makes sense only in that...

Are you trying to make a numeric comparison against the data? That won't work in SQL Server because the "+" (or "-") sign has to be leading, not trailing....

That's a silly comment because 1960s basic wouldn't allow a "-" (minus) in a name anyway!

a-b was perfectly...

Is the name "IDeleted" on the INSERT statement just a typo for "IsDeleted", as it appears on the table? Or could the mistyped column name be causing you the...

Jeff Moden (12/7/2012)

---

Rob-350472 (12/7/2012)

---

I tried with 0x0a as the rowterminator instead but it generated the same results, I need to play some more with this (I've only used it once...

Replication could be problematic as SQL will replicate the DELETEs as well as the INSERTs.

Also, do you need to capture UPDATE activity or just INSERTs?

Finally, are you on Enterprise or...

I would think the old, trusty MAX() would be clearer and less overhead than the mirrored function:

DELETE FROM tn

FROM dbo.tablename tn

INNER JOIN (

SELECT location, MAX(bookid) AS...

Yes, if you can, it would be much better to store from and to currencies as separate columns.

But, either way, you don't need to store 2 conversion rates, only one,...

--If the final total will be <= 24 hrs, you can do this:

SELECT CONVERT(char(5), DATEADD(MINUTE, DATEDIFF(MINUTE, STUFF(STUFF(date_column1, 9, 0, ' '), 12, 0, ':'), STUFF(STUFF(date_column2, 9, 0, ' '), 12,...

One or more them could also be exception/override tables. They may be empty in your case because currently you don't have any exceptions to normal processing rules/conditions. But...