If your project has a database and you are not using a Database Project you are missing out, and causing yourself a lot of unnecessary pain. It basically just organises your schema files to make them easy to maintain, like cs files in a c# project. It has tools to do comparisons and schema updates that make it essential.
Having said that, if you have a product that you ship to 100's or 1000's of clients I find using migrations is easier to maintain the database. > > >> File -> New -> Project -> SQL Server Database Project. Prepare to be >> amazeballsed. >> > > I've only ever seen a colleague use one of these to write code that > migrated an Oracle database to SQL Server. I never looked inside it. Am I > missing something good (for coders)? > > >
