Please... see the URL in my signature...

First, not enough data... without an extra column (hopefully, a PK) to identify the sort order, there's no way to do an update because SQL Server will not know which...

Sigh... if only everyone were...

JohnG (2/22/2008)

---

Thanks Jeff for this reminder.

What we also need to eliminate are:

1. The postings where the poster didn't even bother to look at the online documentation (Books Online aka BOL)...

Just gotta have more than 1 tip per article... thanks for the feedback, J.

Table_A should have the clustered index on the ID column for the tables you have shown. Otherwise, not enough info...

Write the query you want and tune it by looking...

I test all code I post so the answer is, "YES", the code is correct. Please post the error you are getting.

Same goes in 2000... in fact, our standards recommend trying the WHERE NOT IN before trying the OUTER JOIN fore exclusions of this nature.

Or, you can go straight in...

[font="Courier New"]DECLARE @SomeDate VARCHAR(20)

SET @SomeDate = '19-05-2008 09:46:35 AM'

SELECT CONVERT(VARCHAR(20),CONVERT(DATETIME,@SomeDate,105),126)+'.00Z'[/font]

Wouldn't INSERT/EXEC do the job you're looking for?

System date format needs to be set to dmy server wide. I can't, for the life of me, remember how to set it server wide, but a trip...

Does the production machine use VM by any chance? Does it have auto-shrink turned on, especially on TempDB by any chance?

I agree... adding an IDENTITY column to the table will take care of it.

And, Sequence tables are notorious for causing deadlocks in SQL Server because most folks don't write the...

37 to 65 milliseconds.

If you're using WinZip, you'll need the "pro" version, which comes with command-line abilitites, and a trip to the "shell", what ever it's called in SSIS.