Compare the OPTIMIZE_FOR_SEQUENTIAL_KEY property of an Index
By default this is 'off' in SQL 2019. But we have found some tables have significant performance improvements for load if its 'on'. Thus tuning requires these indexes to be on. For SQL Compare to remain useful it needs to highlight were where there is a difference in the property - and support deployments with the property to retain it as on.