• OK, perfect. That helps tremendously. A few more questions on how to accomplish this, as you can probably guess by now we have NO source control on our SQL Servers at all at this point and something that I deperately want to change:

    1. When creating the project for an existing DB that has many tables, views, sps, triggers, etc is there an easy way to create all of these script files other than scripting each one individually?

    2. Can you give me a sample of what a project would look like?

    (i.e. Tables

    CUSTOMER

    CONTACT

    etc

    SPs

    add_customer

    add_contact

    etc)

    3. Is there a way to label what scripts go together? For example, when working on a development project and I am modifying 2 table scripts and 2 sp scripts is there an easy way to show that these were changed for this one specific development project?

    Thanks for all of your input! Your thoughts are extremely helpful to me and I hope will better organize our development efforts moving forward!:D