March 16, 2019 at 12:12 pm
Jeff Moden - Saturday, March 16, 2019 10:42 AMEirikur Eiriksson - Saturday, March 16, 2019 8:10 AMSiva Ramasamy - Wednesday, March 13, 2019 11:33 AMAll,
Thank you for looking into my question. I am facing an issue with difference in checksum calculations for the same data between an on-prem SQL Server 2016 and the Azure version.Here is the scenario.
I have an on-prem SQL 2016 database and a SQL Azure database. The schema is exactly the same between these two databases. I updated the Azure database using the SQL 2016 as the source.
After updating, I was expecting the checksum calculation between the tables for the updated rows to be the same, but it is not.
Has anyone seen this issue before?
the source and destination has numeric and char datatypes only.
Can you post the DDL and DML for both sources, the hash statement and some values where you are seeing different results please?
😎
If you are correct, this is a bug!Maybe not... we don't actually know that the OP "updated" the data correctly. The difference in the HASHBYTES might be screaming that's true.
he, he, come forward now or stay for ever silent :exclamation:
😎
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply