Allow SQL Compare to ignore difference due to ALTER and CREATE
When comparing a VS 2012 database project to a database, when the only difference is ALTER vs. CREATE (which happens because a stored procedure ALTER was executed directly, then saved) the comparison fails. An option to ignore this difference would be very handy.
James Menzies commented
the CREATE OR ALTER syntax really needs to be supported. It is so much cleaner than the alternatives that previously existed.