Forum Discussion
Community ChampionIR with no Collission
smpa01 I think you can rely on GUID because the chances of it being a duplicate is extremely low
https://betterexplained.com/articles/the-quick-guide-to-guids/
1/(2^128) * 1/(2^128) = 1/(2^256)
which will return 8.63617e-78 so that's 78 zeroes after decimal and then 8636 so 0.0000000000000000000000000000000000000000000000000000000000000000000000000000008636 which is very low probability of 2 GUIDs being the same.
Community Championsmpa01 I think you can rely on GUID because the chances of it being a duplicate is extremely low
https://betterexplained.com/articles/the-quick-guide-to-guids/
1/(2^128) * 1/(2^128) = 1/(2^256)
which will return 8.63617e-78 so that's 78 zeroes after decimal and then 8636 so 0.0000000000000000000000000000000000000000000000000000000000000000000000000000008636 which is very low probability of 2 GUIDs being the same.
Community ChampionWhile NEWID() is awesome, I have experimented in last few weeks whether a column created through DAX (instead of PQ) in a table that has IR is immune to IR or not. It turned out that DAX values are not getting duplicated.