RE: SQL Collection Duplicating a DB

[michael@xxxxxxxxxxxxxxxxxx]

It probably will, especially if there are referential constraints that
preclude adding records to a table when it needs records already
present in a different table. I would bet there are APIs that would
identify the constraints. You could then CPYF the data to the new
tables, and then apply the constraints with the ADDPFCST command. Bet
you could do something similiar with journals, too.

> -------- Original Message --------
> Subject: Re: SQL Collection Duplicating a DB
> From: Mike Wills <koldark@xxxxxxxxx>
> Date: Tue, April 12, 2005 3:01 pm
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> There is contraints on these tables as well... would that matter?
> 
> On Apr 12, 2005 1:42 PM, michael@xxxxxxxxxxxxxxxxxx <
> michael@xxxxxxxxxxxxxxxxxx> wrote:
> > 
> > How about listing the table names to a file, then reading through the
> > file, and use CPYF from the old to the new?
> > 
> > > -------- Original Message --------
> > > Subject: SQL Collection Duplicating a DB
> > > From: Mike Wills <koldark@xxxxxxxxx>
> > > Date: Tue, April 12, 2005 2:34 pm
> > > To: Midrange_Midrange-L <midrange-l@xxxxxxxxxxxx>
> > >
> > > I know there was some discussion on this a week or two ago with David. 
> > We
> > > are trying to create a duplicate SQL COLLECTION as a test DB. I know I 
> > can't
> > > save and restore as a new name. So how would I go about copying all of 
> > the
> > > data to the new DB? I have the tables setup, I just need to copy the 
> > data.
> > >
> > > My vendor has a utility to do this, but it takes forever. It first 
> > creates a
> > > dump of the DB (about a 17 GB file) onto the IFS, then they have me do 
> > an
> > > import. Problem is this import ran for over 24 hours and wasn't complete
> > > yet. I let it run over 36 hours before I cancelled it. That is not 
> > really
> > > acceptable timeline for me. Plus you need to basically have three copies 
> > of
> > > the DB on your server at once. That isn't exactly ideal when we have 
> > limited
> > > amount of disk space.
> > >
> > > Any ideas on how to do this?
> > >
> > > --
> > > Mike Wills
> > > Midrange Programmer/Lawson Software Administrator
> > > koldark@xxxxxxxxx
> > > http://mikewills.name
> > > Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.
> > > --
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> > list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > 
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> > 
> > 
> 
> 
> -- 
> Mike Wills
> Midrange Programmer/Lawson Software Administrator
> koldark@xxxxxxxxx
> http://mikewills.name
> Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.