SQL Compare does a great job of trying to help you map columns in your database. For example, I was testing deployments recently to see how a process might work and I noticed the SQL Compare had automapped columns for me.
This is a feature in SQL Compare that tries to make your development effort a little quicker and easier. As you can see in the image below, there’s a note at the top of the comparison, and then an indicator for the actual object.
If I click the object, I see the code, but I don’t know where the auto mapping has taken place.
In this case, I know because I changed the Quantity column name, but there’s nothing special here about the mapping. SQL Compare just mapped “Quantity” to “Qty” by itself. If I check the project properties, I can see the mapping, and change it if necessary.
If you want to know how to customize this, I’ve got an article on the Redgate Hub on How to Customize Schema Comparisons using Auto Map in SQL Compare.
Automap is one of those useful, handy features of SQL Compare. It gets you moving in development quickly by taking care of some work, but you can easily change things and keep your project handy if you have the need.