?
It can do that, but it won't automatically. You have to configure the deployment plans. Think of the deployment plans as a script that will run each time you deploy to an environment.
For stored procedures, those should be treated as code and kept in source control, as they can be recreated simply with a DROP/CREATE/CONFIGURE script file. This way, they can be redeployed like any other artifact (i.e. extracted to some directory and executed from disk).
As mentioned in the previous post, DDL/DML database changes cannot be automatically rolled back because once you DROP a column, it's gone for good until you restore from backup. Configuring a deployment plan to take a database backup is probably a good idea in this case :) You could go one step further and configure the deployment plan to restore from that backup on some condition if you really wanted to, but I would hope once the deployment is automated that these failed deployments will be kept to a minimum.