Usman,

Charles is right, an IDENTITY column might help to guarantee row uniqueness is this case.  However, whether you have an IDENTITY column or not (sometimes can't change a table because...

Like I said, "Rather than using a view, ..."

Don't use @@IDENTITY which can be tricked by triggers... use SCOPE_IDENTITY() instead.

Always assign values captured in @@ROWCOUNT and @@ERROR immediately after the SQL that you want to check.  You can...

Very Nice article.  Covered a lot of ground and it's a pleasure to actually see commented formatted code.  I've seen a method to write to text files using linked servers...

Yup... I know the feeling... you should see the one at work. Glad to help.

Dunno, maybe I missed something....

SELECT

 E.PAYTYPE

, SUM(CASE datepart(dw,E.TimeDate) WHEN 2 THEN E.Hours ELSE 0 END) as Monday

, SUM(CASE datepart(dw,E.TimeDate) WHEN 3 THEN E.Hours ELSE 0 END) as Tuesday

, SUM(CASE datepart(dw,E.TimeDate)...

It's a bit difficult to believe that you would ever have a NULL StartDate with a valid EndDate.  Normally, it's the other way around.  But, no worries...

For NULL StartDates, I...

Antares,

I apologize if the time lag between our posts caused this...

I had reposted a solution as follows...

STUFF(STUFF(REPLACE(STR(Run_Time,6),' ','0'),5,0,':'),3,0,':')

The original question was how to convert the Run_Time column of...

p.s.

If you are getting a "NULL' as a return, perhaps the code you wrote isn't actually finding what you think.  Post your code and we'll take a look.

Schalk and Antares,

I test this stuff before I post it and, you are incorrect.   STUFF works just fine on an INT values thanks to implicit conversions.  For example, this...

Autogrow = Fragmentation

As some have already said on this thread, set TempDB to be a reasonably large initial size and set autogrow to100 to 500 mb.  We currently have a...

Since the column is in the format of HHMMSS (even though it's a number),

For just a pure string representation of the time...

STUFF(STUFF(run_duration,5,0,':'),3,0,':')

For a real time as a...

You may experience some "wierd" answers when using FLOAT because it does it's math in a binary rather than decimal fashion.

The problem is most likely that the datatype in one of the columns is FLOAT which using binary math instead of Decimal math with some very unexpected results.  Recommend you...

I believe that your outer parenthesis are the problem.  Compare your script tot the previous answer.