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...

The real killer would be the presence of a clustered index or a great many non-clustered indexes.  Unless you use SELECT/INTO, the Simple Recovery Mode won't be of much help...

What do you want the CSV file to look like for column headers?

Would be a bit more helpful if you posted the code so we can see what you did wrong.  For example, in the SELECT you posted in your message, the...

I, for one, have enjoyed the simple yet educated rhetoric spawned by this editorial. The reason for most of the passion displayed is likely because of personal experience and...

Heh... yeah... how silly of me to think it might have been an SQL Server question on an SQL Server forum... not enough coffee and I missed that... thanks, Julie.