Re: Procedure to migrate a procedure

From: Brian Dick <bdick_at_cox.net>
Date: Fri, 15 Oct 2004 16:32:11 -0400
Message-ID: <49vncxuztqtl$.7y3sy7isgldq$.dlg@40tude.net>

On 15 Oct 2004 05:02:59 -0700, Richard Elliott wrote:

> Brian Dick <bdick_at_cox.net> wrote in message news:<p0xc8jgs5s8y$.1kikyxgavjkpx$.dlg_at_40tude.net>...
<snip/>

>> 
>> Migrating source from instance to instance is error prone and has
>> irreproducible results. You should be building your databases from source
>> control using shell scripts or ant (my favorite). Scripts can be tested,
>> tested, and tested again. Scripts give you a systemic process you can
>> improve. And you can log their actions.

>
> Brian, that sounds like what I want to do. Logging is a big plus. By
> source control do you mean something like Visual Source Safe or one of
> versioning applications ? I'll do a google on ant. I appreciate all
> the input on what I should be doing in place of what I am doing now. I
> already know I need to do it differently. What I'm looking for is
> specifics on how to do it better/different. I'm not a trained DBA
> (DUH) but have inherited the migration tasks for the application I
> support. I want to do it right, but could use some specific (examples
> ?) help getting there from here. Thanks in advance for all the help so
> far.

Sure VSS will work. That's what I'm using now. I have used ClearCase and CVS in the past. CVS would be my first choice, if I had a choice.

I like ant over shell scripting because ant is designed specifically for doing builds, whereas shell scripting is more general purpose. But if shell scripting is your game, go for it. Received on Fri Oct 15 2004 - 15:32:11 CDT