How do you determine that?

This was executed on 2008. Should I see this in my system tables? Maybe our install did not add this?

Thanks got it to work.

Yes that did the trick. Thanks ever so much.

Now the user would like me to get rid of both records in question since we have identified this as being a duplicate record. How would I do that?

Thanks

Thanks you ever so much. This solved my problem.

Thanks for the code snippet - it works really well. Also, thanks for the link to 'Best Practises' when posting a question. Very helpful and something I'll remember...

Yes, and it still did not work.

I used this as an example:

select * from mytable where isnull(ltrim(rtrim(status)),'')<>''

works great!!!!

Thanks ever so much. That worked great.

Thanks. Yes the DISTINCT shouldn't be needed here because there should be no duplicates returned back in the results. The primary Key is Party_Id. That is where...

I added an insert at the beginning of this select statement to see if I could find out what the problem was and ran it from SQL Server Management Studio....

Works like a charm...exactly what I want. Thanks for all your help!!!!

A User request. We probably could have gaps because the Seq_Num will be used as a key but they wanted it to start at 1 and go up by...

I will be using a strored procedure to take the results and load them to another table using SSIS. They want the seq_num to start at 1 and go...