[dba-SQLServer] Source code version control

Then you're away to the races! Follow the VS.NET instructions that I gave
you to the letter, save the part about *Run*, since your databases already
contain the objects that the Create scripts would create.

Since your backup space is unlimited, if I were you I would go back at least
one significant build in the project(s) of interest, and recreate it|them,
then follow the instructions for VS.NET+VSS. Repeat for each build of
significance. After restoring each build, you can destroy the previous. Add
each build to VSS as a separate project. (This is not how you would do it in
practice, but it's a good way to get all the previous history in.)

Once your current build has had all its Create scripts generated, then you
can begin doing it right, which is to say, generate the scripts, add them to
VSS -- which will lock them, and from then on check out only the sprocs etc.
that you need to change. Check them out, fix whatever, then check them in.
Add a comment about what was changed and why.

This is beautiful with team projects because nobody can check out something
somebody else has checked out.

In a few places I have worked, everything related to a given project (Word,
PPT, databases, the whole nine yards) was stored in VSS. Since I realized
that VSS could do all that, I have adopted this strategy for my own practice
as well.

Arthur


On 6/7/07, Robert L. Stewart <rl_stewart at highstream.net> wrote:
>
> See comments below...
>
> At 12:00 PM 6/7/2007, you wrote:
> >Date: Thu, 7 Jun 2007 07:04:00 -0400
> >From: "Arthur Fuller" <fuller.artful at gmail.com>
> >Subject: Re: [dba-SQLServer] Source code version control
> >To: dba-sqlserver at databaseadvisors.com
> >Message-ID:
> >         <29f585dd0706070404i488d7fd8mda06e8c46d5c75b8 at mail.gmail.com>
> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >
> >Your general strategy is correct, IMO, but I would be tempted to take it
> a
> >little further into the past, if possible. This depends on the state of
> your
> >backups and available disk space. Think back to milestones of significant
> >change and see if you have backups before and immediately after such
> >changes. If so, then if I were you, I would start there, and build up a
> >history in VSS that culminates in the current build.
>
> Essentially, backup space is unlimited. All instances are the same
> except for the importing of accounting information in one of them.
> It is the only one doing it. The plan was to have a full export of
> DDL for all objects as a baseline. Just not saving them individually.
>
> >So. Two possible situations pertain: do you have VS.NET <http://vs.net/>
> or
> >not?
>
> Yes, I have an MSDN Universal subscription, so I have everything. :-)
>
> We have VSS being used for the ColdFusion stuff now. So that is completely
> in place.
>
> Thanks for the pointers.
>
> Robert
>
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>