HP3000-L Archives

October 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Dirickson b894 WestWin <[log in to unmask]>
Reply To:
Steve Dirickson b894 WestWin <[log in to unmask]>
Date:
Thu, 9 Oct 1997 13:21:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
>We currently have only one Turbo Image Database on our system. This is
our
>production database.  I would like to create a development database we
can
>use
>for program modifications and testing.
>
>Is it possible to create a development database from a production tape
>backup?
> Keep in mind that We may want to use a different name for our
development
>database?  Are there any problems or subtle differences we need to be
aware
>of
>by doing this?


Assuming that you have a separate account for development, just :RESTORE
the database to the desired group in that account using the ;LOCAL
option. Or copy it with one of the tools like Adager. Or use the
capability provided by Flexibase (and probably others) to create a
"sample" database by subsetting a real database according to selected
parameters. As others have mentioned, the more the development account
looks like the production account, the less hassle you'll have.

As for names, it shouldn't matter; you should be using "dummy" names for
your database accesses anyway, so that you can point any given program at
an arbitrary database using file equations. Your software can use a
"generic" name like "PROD" in its DBOPEN calls, and you can point the
PROD formal file designator wherever you need it to go.

Of course, this is my opinion, and is unconditionally guaranteed to be
worth every penny you paid for it ;-)

Steve

ATOM RSS1 RSS2