it means you have values in your varchar fields that either are not numeric and cannot be cast to a int or they are a value that falls outside of...

Yes the function will be called twice and as for the difference between the RBAR version and the select, you have to test.

We can't say the duplicate evaluation...

if you have to call a UDF for each insert, by definition you have to RBAR it. I'm curious why you have to call a function before each insert...

I'm not sure why you would ever have to do something like this unless you had a bad data model to start with but also followed some specific rules. ...

Now, this may sound naive...but do you work hard to get the raise or do you work hard because it is its own reward. Sure, getting a nice raise...

Couldn't you just use the ISNUMERIC() function on that field and anything with a zero won't cast to an int?

Your welcome! Anytime.

sorry about that. i forgot to remove the UP references....

SELECT UP.TableRecordUID

...

This should help:

SELECT UP.TableRecordUID

,UP.CreatedDate + UP.CreatedTime AS 'CreatedDateTime'

...

Not to be rude, but are you just searching for #? It would only return one if you ended up searching for 'drop table #'

Here's the foundation of what you need: (there are some tweaks you'll need though for the zeros and first/last records)

select T1.Serial, (T1.I_C_O - T2.I_C_O) as Positive, (T2.I_C_O - T1.I_C_O) as...

i don't understand your comment.

how do you know it doesn't? It want way doesn't it work? (I know it won't for encrypted procs, but other than that it looks ok).

Whats the order of the data? If you want to compare rows like that, they should have a logical order in the data and it only appears you have...

did you paste the exact error? It states something about converting 'Waive' to an int. You have 'Waiver' in your example.

please double check...