I can't upload the Image to SO for some reason so see the imgur screenshot here#1 and here#2 and here#3.
[edit] In 3rd example, the only diff emphasis is on the keyword CREATE (casing problem) while view can be in lower, no problem. What, why?!
I have "Ignore Keyword Casing", "Ignore Whitespace", "Ignore Comments", "Ignore Semicolon" and still, I get diffs in casing of IS NOT NULL vs is not null.
This is a huge problem since it triggers rewrites/reindexing on large tables that should not be touched. I know and have the workarounds for this, but that's not the point. I'd like to be able to use this tool when needed in a reliable way.
So, am I doing something wrong here? Is this tool actually usable? Can I do anything to fix this outside of recasing an entire Project for absolutely no reason at all... or stop writing my DDL by hand since Microsoft can't handle lower casing or the ANSI cast?
PS: I have the latest SQL Server (not Preview), latest SQL Package.
[edit] Versions: VS 2022 17.14.4, SQL Package 170.0.94.3, SQL Server 2022.
I found the solution: it's Redgate SQL Compare. Microsoft ftw!
This tool understands lower case is the same as upper case and offers even more help in migrating. And for this very niche need... it is what it is.