No such thing in SQL Server 2000.  You can make one with a trigger on each table and a "LastModified" table... just be careful not to make any deadlocks...

Some hard disk systems (SAN's, etc) come with clone and snapshot systems that will do this in scant minutes for a half-terabyte database.

There isn't one in T-SQL. 

Um... not sure... but I think you may have missed the point...

What does the "executable" actually do?  And for how many rows per call does it do it?

Eamon,

Drop the target table (takes indexes with it) and do a SELECT collist INTO tgttable FROM srctable WITH (NOLOCK).  Then, reapply your indexes.  If it takes more than 10 minutes...

Heh... Thanks David...

I've been doing a lot of BCP work lately and ran into this ol' post of mine... Yeah, I know it's a forum and we shouldn't expect...

Ya know, Brenda... a little feed back on this extent of this type of help would have been appreciated.  At least let me know how it worked out for you...

sp_Help tablename is what most folks are looking for.  Similar to "describe" in Oracle.  Lemme know if that's not quite what you wanted.

Madhuri,

There are several ways to do this... most of them are covered in the following URL...

http://www.simple-talk.com/sql/t-sql-programming/sql-server-excel-workbench/

First, you might want to tell how you'd do that.

Second, the request was specifically for how to do it from a stored procedure.

Even if you say, "It's fifteenth normal form, Google it, Skippy" that will be a big help.

It is...

Try using ISDATE(expression) in a SELECT to find the bad data... See BOL for more detail on ISDATE.

If you want better performance, use derived tables instead of WHERE IN or WHERE EXISTS.

What's wrong with your NOLOCK is just what Serqiy said... because it's not in parenthesis, the word NOLOCK is being used as a table alias and not a table optimizer...