VS 2012 Ultimate RC does not seem to have any support for the Data Compare feature that was present in VS 2010 Ultimate and that saved me a ton of time (not to mention cash) when comparing the data between 2 databases and generating deployment scripts.

With regard to database diagrams, these were also supported in VS 2010 but do not seem to be supported at all in VS 2012, diagrams are useful way to quickly see the structure of a database and yes I know I can use SSMS but as this is built on top of VS 2010 would it be so difficult to add this support to VS 2012?

Currently when you run a Schema Compare through the Database Tools in Visual Studio 2012 you have the option to Generate a SQL Script or Run the Updates against the Target Database Directly.

I propose an additional option, a Printable "Report View" that shows all the objects and the differences. This could be as simple as being able to print the grid (expanded) that is generated from within Visual Studio along with some basic statistics such as:
1) The number of Total Objects Compared
2) Number of Objects in Source that are not in Target
3) Number of Objects in Target that are not in Source
4) Number of Objects to be updated in the Target

In some organizations production apps are only allowed to communicate with a database through stored procedures, including basic features like SELECT, INSERT, UPDATE, AND DELETE. As a result, when creating a new table stored procedures must be created for each of those functions. While not difficult to do, it is incredibly tedious and time consuming when working with a lot of tables.

It would be nice if a SQL Server Data Tools (SSDT) project had the option to automatically script stored procedures for a table or a view. SQL Server Management Studio has a somewhat similar feature with Script As, however it would be nice to take it a step further by having the ability to generate input parameters as well.

Even without the development requirement mentioned in the first paragraph, the ability to automatically generate stored procedure scripts to some degree could greatly increase productivity and reduce the tedium of creating certain procedures.

I have a few stored procedures in my database project that reference local temporary tables created in another stored procedure. The procedures throw SQL71502 Warnings, that tell me the procedure has an unresolved reference to the temporary table. There is no way to resolve these Warnings within the Database Project, since there is no way for the Database Project to "see" the temporary table created in the other procedure. Therefore, the only choices I have are (1) keep the Warnings in the solution or (2) suppress all Warnings of type SQL71502 in the project. Neither approach is optimal. Keeping these Warnings just creates noise in the development environment, while suppressing ALL Warnings of this type might lead me to miss an unresolved reference that CAN be resolved. I would like to see a feature that would allow me to suppress a specific Warning on a specific object. This way I can remove the Warning from the development environment without having to suppress all Warnings of that type.

Currently when we make a change to a single object such as stored procedure,view, function , trigger we need to switch the CREATE statement to ALTER, apply the change and then switch back the ALTER to CREATE. Failure to do so results in an error "SQL03070: The statement is not recognized in this context". This causes build to fail. The ALTER at the beginning should be allowed atleast for objects that frequently modified such as stored procedures, views, triggers and functions.

We would like to enourage a practice where developers can check out the object from the DB project inTFS, apply the changes to the database and check in the changes. The switch back to ALTER is an additional step that the developers have to do before object check-in.