Hi,
It appears that binary_checksum can give the same checksum for
different strings, which is a bit worrying. (I guess the algorithm is
the problem in the context of a repeating pattern.)
e.g.
select binary_checksum('A')
,binary_checksum('AAAAAAAAAAAAAAAAA')
,binary_checksum('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA A')
,binary_checksum('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAA')
My question...
Is this approach to generating checksums adequate for managing the
object scripts in the SQL Server to ensure that they haven't changed. I
guess that the probability of somebody making a change to a script and
ending up with the same checksum is almost negligible. Has anybody used
this approach in an FDA validated production environment, i.e. 'no ifs,
no buts'? Would it stand up to scrutiny?
Any experiences, thoughts?
Regards
Liam