CSDunn,

You can either use the forumla in the following in a UDF or directly...

SELECT DATEADD(yy,[Last Sale Date]/1000-1900,[Last Sale Date]-([Last Sale Date]/1000*1000)-1) AS [Last Sale Date]
  FROM dbo.tblPaymHistCurrentWeek

-1900 Serqiy

A view that looks like the following would certainly do it (untested)...

 SELECT d.FirstName   = MIN(CASE WHEN d.PropertyName = 'FirstName'   THEN d.PropertyValue ELSE '' END),

        d.LastName    = MIN(CASE WHEN d.PropertyName...

Wayne,

Whether I agree with the premise of using WITH (NOLOCK) or not, your post did what all good posts are supposed to do... spark pro/con conversation.

Thought I'd reward you...

Tony Rogerson's blog he has code which demonstrates this. http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/11/16/1345.aspx

That code, once you actually get the data...

James,

Would you mind posting both versions?  I'd like to do a little testing to see what's up... thanks.

Ramesh,

Thanks for the feedback...

Unless your payroll process has hierarchical payments such as those found in an MLM, I'm pretty sure that we can help you figure out a way to...

Heh... ya... hence the need for the article.  Thanks for the reminder

Its a bit difficult... I have a hard time thinking in a non-set based fashion when trying to write the cursor examples 

Then you need to use something like what DC Clark posted based on a date column...

Thanks for the feedback, Gova... much appreciated.

What does an SP do that needs to execute "at least 200+" times per user?

Not listed?  It's listed as "Set Option Changed in Batch" and "Set Option Changed".  And they kinda tell you how to build a test... create a proc with theoption you want...

One of the other problems with Cursors AND While-Loops is the number of resources (mostly cpu time) they use when compared to properly written setbased code... the following example code is...

Shoot... didn't mean to make it sound like I took it any other way... guess I need to use more smiley faces