Re: Disabling redo and rollback

Hmmm.. ok.

This may be too obvious and you have hopefully already considered doing this, but here goes.

Disable unique and primary key constraints and drop all indexes ... during the import.

"Phil Kaufman" <philk_at_dbcsmartsoftware.com> wrote in message news:f7UW9.87$ld5.9119846_at_mantis.golden.net...
> Good question.
>
> It's simple, we needed a product that could export and import between
> different vendor database engines. Since there isn't a great selection of
> products available on the market that do this, we decided to build our
own.
> You see our flagship product runs on various database back-ends, so just
> imagine the possibilities if we had something to take data from one
database
> to another (cross vendor), without any issue.
>
> Well, it works rather well, and I simply wanted to improve the products
> performance for Oracle imports.
>
> Thanks to everyone's response anyway.
>
>
> "JustAnotherDBA" <jadba_at_bellsouth.net> wrote in message
> news:Rz6W9.7086$F_3.4520_at_news.bellsouth.net...
> > You have written an in-house export/import program ?!
> >
> > Just curious, why would you want to re-invent the Oracle export/import
> > utility.
> >
> > "Phil Kaufman" <philk_at_dbcsmartsoftware.com> wrote in message
> > news:B4_V9.13$A9.2345076_at_mantis.golden.net...
> > > Folks,
> > >
> > > My environment is Oracle 8.0.5 and higher/Windows 2000.
> > >
> > > My question may seem fairly novice, but here it is. I have written a
> > > in-house export/import program, which works on multivendor databases.
> At
> > > any rate, I was wondering if it is possible to disable the redo and
> > rollback
> > > for a transaction that does the import, and if so, how exactly I would
> do
> > > this, and if so, what kind of improvement in performance can I expect.
> > >
> > > Thanks!
> > >
> > >
> >
> >
> >
>
>
Received on Mon Jan 20 2003 - 13:04:48 CST