Show us the INT value for '5/10/2007' and we'll be able to tell you (but I think you're wrong about the date)

Um... just making sure... you're saying that the current size of TempDB is over 166 GIGA BYTES ???

I'm...

Oh... almost forgot... if the code uses MAX(someid)+1 to determine the next "Key" or uses @@IDENTITY (SCOPE_IDENTITY is OK), that may be the source of the "Key" being out of...

Here's a powerful hint... the "key" this error message speaks to is either a "Primary Key" or a column with a UNIQUE index (usually a "Primary Key" for this error).

Ah, sorry... that's too much info...

This will do it without a loop... again, if you get negative numbers for rows for some tables, you will need to do a DBCC...

Could be a couple of things, but let's go for the simple side, first.

Try adding the WITH RECOMPILE option to the stored proc... you may be fighting something bad that...

Actually, I believe this is what they call a "UNIX DATETIME" and it represents the number of milliseconds since the midnight on 01/01/1970.  That also makes your 5/11/2007 date incorrect (unless...

DBCC SHOWCONTIG WITH TABLERESULTS

... will show you a whole lot more than just table names and rows. 

If you get negative numbers for rows for some tables, you will need...

For Windows XP... TaskMgr.exe

That'll be one case of beer for asking questions outside the scope of SQL Server

I believe this will do.

SET DATEFIRST 7 --Default for SQL Server

SELECT GETDATE()-DATEPART(dw,GETDATE())-2

Like this...

SELECT CONVERT(CHAR(10),CAST('Mar 20 2007 3:57pm' AS DATETIME),111)

Of course, you would sub a couple of things to use against a table...

SELECT CONVERT(CHAR(10),CAST(yourdatestringcolumn AS DATETIME),111)

FROM yourtable

That's actually a pretty good plan and I agree with that... nice to see someone to spend a little time up front to save wads later on.

Exactly... (and great explanation, by the way)   I know that and you know that and even some other folks know that.  And, you're absolutely...

1.  Doesn't matter if the header doesn't have the same number of delimiters.  BCP is picky that way.

2.  That's because of what I said before... you must delimit the end...

Man, I gotta remember to check for those...