Re: [Info-ingres] Transaction log size (was Huge copy out/in)
- From: "Paul Andrews" <ac297@xxxxxxxxxxxxxx>
- Date: Thu, 15 Jun 2006 13:59:15 +0100
I haven't followed this thread too closely, but here's an 'outside the box'
suggestion..
Instead of trying this unload/reload as a single hit, would it help to do an
ascii unload then use a script to divide up the data into smaller files
(this is quite easy)? You could then run a batch of copy.in scripts to
reload the smaller unloads back into a single table. This would avoid the
limits problem you may be hitting and stop your problems of filling the
transaction log.
You could even, at a pinch reload the smaller data files into different
tables and then (using SQL) insert them back into the main table after
loading - that way you could run the copy.in scripts simultaneously.
I'd even suggest slicing up a binary unload, but I think it might be too
dangerous..
Apologies for the belt and braces suggestion - kinda the way I approach
stuff..
Paul
.
- Prev by Date: RE: [Info-ingres] Transaction log size (was Huge copy out/in)
- Next by Date: RE: [Info-ingres] Transaction log size (was Huge copy out/in)
- Previous by thread: RE: [Info-ingres] Transaction log size (was Huge copy out/in)
- Next by thread: RE: [Info-ingres] Transaction log size (was Huge copy out/in)
- Index(es):
Relevant Pages
|
|