------=_Part_5855_26718264.1209418666552
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Jonah,
Thank you for the answer. Good to know about this enterprise DB feature.
I=B4ll follow using pgloader.
Regards.
Adonias Malosso
On Sat, Apr 26, 2008 at 10:14 PM, Jonah H. Harris <jonah.harris@[EMAIL PROTECTED]
>
wrote:
> On Sat, Apr 26, 2008 at 9:25 AM, Adonias Malosso <malosso@[EMAIL PROTECTED]
>
> wrote:
> > I=B4d like to know what=B4s the best practice to LOAD a 70 milion
rows,=
101
> > columns table
> > from ORACLE to PGSQL.
>
> The fastest and easiest method would be to dump the data from Oracle
> into CSV/delimited format using something like ociuldr
> (http://www.anysql.net/en/ociuldr.html)
and load it back into PG using
> pg_bulkload (which is a helluva lot faster than COPY). Of course, you
> could try other things as well... such as setting up generic
> connectivity to PG and inserting the data to a PG table over the
> database link.
>
> Similarly, while I hate to see shameless self-plugs in the community,
> the *fastest* method you could use is dblink_ora_copy, contained in
> EnterpriseDB's PG+ Advanced Server; it uses an optimized OCI
> connection to COPY the data directly from Oracle into Postgres, which
> also saves you the intermediate step of dumping the data.
>
> --
> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
> EnterpriseDB Cor****ation | fax: 732.331.1301
> 499 Thornall Street, 2nd Floor | jonah.harris@[EMAIL PROTECTED]
> Edison, NJ 08837 | http://www.enterprisedb.com/
>
------=_Part_5855_26718264.1209418666552
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<div>Jonah,</div>
<div> </div>
<div>Thank you for the answer. Good to know about this enterprise DB
featur=
e.</div>
<div> </div>
<div>I=B4ll follow using pgloader.</div>
<div> </div>
<div>Regards.</div>
<div> </div>
<div>Adonias Malosso<br><br></div>
<div class=3D"gmail_quote">On Sat, Apr 26, 2008 at 10:14 PM, Jonah H.
Harri=
s <<a
href=3D"mailto:jonah.harris@[EMAIL PROTECTED]
">jonah.harris@[EMAIL PROTECTED]
>&=
gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px
0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class=3D"Ih2E3d">On Sat, Apr 26, 2008 at 9:25 AM, Adonias Malosso
<=
<a href=3D"mailto:malosso@[EMAIL PROTECTED]
">malosso@[EMAIL PROTECTED]
>>
wrote:<br>&g=
t; I=B4d like to know what=B4s the best practice to LOAD a 70 milion rows,
=
101<br>
> columns table<br>> from ORACLE to PGSQL.<br><br></div>The fastest
a=
nd easiest method would be to dump the data from Oracle<br>into
CSV/delimit=
ed format using something like ociuldr<br>(<a
href=3D"http://www.anysql.net=
/en/ociuldr.html"
target=3D"_blank">http://www.anysql.net/en/ociuldr.html</=
a>) and load it back into PG using<br>
pg_bulkload (which is a helluva lot faster than COPY). Of course,
you=
<br>could try other things as well... such as setting up
generic<br>connect=
ivity to PG and inserting the data to a PG table over the<br>database
link.=
<br>
<br>Similarly, while I hate to see shameless self-plugs in the
community,<b=
r>the *fastest* method you could use is dblink_ora_copy, contained
in<br>En=
terpriseDB's PG+ Advanced Server; it uses an optimized
OCI<br>connectio=
n to COPY the data directly from Oracle into Postgres, which<br>
also saves you the intermediate step of dumping the data.<br><font
color=3D=
"#888888"><br>--<br>Jonah H. Harris, Sr. Software Architect | phone:
732.33=
1.1324<br>EnterpriseDB Cor****ation | fax: 732.331.1301<br>499 Thornall
Stre=
et, 2nd Floor | <a
href=3D"mailto:jonah.harris@[EMAIL PROTECTED]
">jonah.harr=
is@[EMAIL PROTECTED]
><br>
Edison, NJ 08837 | <a href=3D"http://www.enterprisedb.com/"
target=3D"_blan=
k">http://www.enterprisedb.com/</a><br></font></blockquote></div><br>
------=_Part_5855_26718264.1209418666552--
|
