No, I got it, it's what I meant

Thanks again and Happy New Year

oh... got it. Right, converting to VARCHAR does it. Got it.

Thank you

• This reply was modified 4 years ago by  btio_3000.

Hi Eirikur,

and I apologize for that too. The reason I did not reply with the execution plan is that there is a lot of changes/testing going on, the "original" database...

What apparently happened was that it was initially tested over remote connection

Timings were taken "physically", still it was a bit faster with UDF, every time... Still not sure why, could...

( just an update: enforcing DATETIME by adding CONVERT( DATETIME, ... ) within DATEADD apparently fixed it... )

Thanks again

Thanks for replying,

Not sure I understand...

like I said both [date2] in dbo.[myTable] and [date1] in #temp t ARE of DATETIME
though it still gives me...

Thank you Evgeny, but does it mean that 

applying WITH (