The SSN is stored as a MD5 hashed value.
The combination of SSN, PKT and FICE_NBR in table A does not have a match on the combination of SSN, PKT and FICE_NBR in table B.
Ah, thanks, Gary. I feel much better now.
Shifting gears a bit, you might want to consider something a little bit more than simple MDF hashing. A simple billion row rainbow table (which is nothing on the machines today) would quickly unravel all of the SSNs. Even adding a salt to the MD5 would be better although that would likely still fail an audit.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs