I have the following Stored Proc (I am not sure it is correct). I just am trying to see if there are any duplicates in the table.

Charles, I agree, but I would prefer a param array and then check if Column Exist for each one before executing the query.  Also a 2nd optional parameter could be use to handle "WHERE conditions like in Terry's case.

So far, I did not have the need for such checking, but since I work on multiple projects at the same time, I like to have my code as generic as possible so it can be reused in all projects, even though I do not have a common assembly for all projects just yet

I am still learning this stuff which always amaze me with simple things and the .Net/SF approach to handle them.  Pure and simple, I just love SF at the same level I loved VFP and my previous framework.  It feels good being comfortable with a tool and I am at that level with StrataFrame now.  (hmmm, Trent, that does not mean I am totally settle,  I still want to see the new StrataListView completed with the automation stuff )

Edhy Rijo

I think your idea of an array for multiple fields is very good, especially in keeping the function as generic as possible.

Just as an aside :  I've been working a lot with using table value parameters in stored procedures and I'm really interested to find that unlike other type of params, you don't need to account for *not* passing the param - the TVP in the sproc will just be an empty table.  Interesting in that you can write where clauses in the sproc that let you receive either a single or TVP param for comparison and it will work depending on what you pass in. 

( reading that over it probably doesn't make any sense unless you've been playing with TVPs but for anybody who has, the TVP as empty table if no param is passed came as a surprise to me and somebody may find it useful )

Hi Charles,

I have not worked with a TVP yet.  I have a consultant "Uri Dimant" which is a MS SQL MVP which helps me with those deep needs and even though he is pretty good explaining this type of things with MS-SQL, sometimes I don't have the luxury to pay to much of attention to details.  He has created some complex stored procedures to deal with millions of records and re-factored those couple of times to take advantage of new functionality of MS-SQL 2008 R2.  In case you or anyone needs serious help with any MS-SQL problem, feel free to contact him.

Edhy Rijo