Version Controlling Database that is used by multiple projects

I'm currently working on a project that has several 'Visual Studio Solutions'. One is for the main application and the others are component-based projects which will be reused in other applications.

The problem is that all three solutions need to access data from the same database. Each component has its own set of views, functions and sprocs but the schema differs in places (one component may require a field that another component doesn't).

Basically, I don't want to have one solution break because of a change that I've made in another one.

The way I see it I have tw开发者_如何学编程o options:

• Create a new project that is referenced in all solutions that purely contains database scripts
• Manage the Schema in the main application solution and the views, functions and sprocs in the other solutions (as appropriate) and be very, very careful when I do a build

Any suggestions would be greatly appreciated.

Thanks in advance,

Jason

Just thought I'd post my solution here just in case anyone else comes across the same problem...

I went with option one in the end. I created a new Database Project which is referenced in all 3 solutions. Not the prettiest solution in the world, but it works.

Thanks again to pranay for responding.