Yeah, I'm an idiot, Lowell.. It's all there.. lol

Thanks again!

Well this is interesting..

Hey, Lowell, try using this in your function and change the int to bigint. I must be missing something because it's not returning everything.

'111111101100010000111100000001'

Thank you both! I found out the same thing about the power() function and was a little surprised but I haven't used it in a while either. I'll try them...

You know, Sean, if I could normalize the data I would but it's third party data and I don't have that option.. good thought though.

Nevermind... if I flatten the hour out of the datetime I can do it. Thanks to SQLPrincess for the co-solution!!

A valiant effort, DVA2007, but you'll note in my first post that I cannot group on Event Name because they are disparate (sorry I mislead you with my test data).

For...

Works just fine on my machine. Anyone else having difficulties with the SQL?

Yes.

Try this.

UPDATE dim.doccontrolprofile

SET DocType = SUBSTRING(STG.CurrDocNumber, 1, 1)

FROM dim.doccontrolprofile dc

INNER JOIN staging stg ON STG.DocContProfileID = DC.DocControlID

AHA!

Thanks, Gail! That's the piece I was missing. The implicit conversion to a string.

Sweet.. something new learned today...something I should have already known.. sigh..

Thanks, Gail, that part I understood. 😀 I was curious about the internal mechanics about the len() function not returning the number of digits in the float.

So if it takes...

So the len() function is counting bytes instead of digits? Is this particular to floats?

*runs for the production server to try this out...*

Sounds like a plan!

~jk.. though I'll take a look at that option and see.

*bump*

Thanks, Steve. I can wish for a magic bullet but I think I'll be rolling up my sleeves for this project.

4:1? Do you know if those were high volume OLTP...