Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a couple of different database projects in an existing solution and I’m experiencing some strange behavior. 99% of the database objects that I define with the projects work just fine, but a handful are not being recognized as part of the project when a schema compare is done. It’s just like they don’t even exist. So far they appear to all be stored procs that are skipped.
I created them just like all of the rest of the objects.
What information might you need to debug this?
I found one reason why objects were not being created. Some of the files were initially created as Script files instead of Stored Procedure files. It appears as though the database project keeps track of which files represent objects that need to be synchronized.
The tick is knowing if you have a database object sql file or a script sql file. One easy way to know you’re in a script file is that they will have a menu bar within the content area (beneath the tabs), where as files created as functions or stored procedures will not. The menu bar has things like Execute, Parse, Connection settings, SQLCMD mode, as well as others.
As pointed out by a colleague, the difference seems to be the Build Action property. The synchronized files seem to all have the Build Action set to Build