| From: | Tim Uckun <timuckun(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | S McGraw <smcg4191(at)mtneva(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Importing directly from BCP files |
| Date: | 2015-11-17 00:25:53 |
| Message-ID: | CAGuHJrOz5p1Mu-rZYc-nJR1ifYJqZgEgqx5sDg2K19=n-OrD2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> the binary form of the BCP file output is undocumented. So if all the BCP
> files you have are the binary(native) version you are up this creek without
> a paddle.
>
>
Ugh. Yes it looks like that's the creek I am on. Thanks Microsoft!
> So, moving to another creek. It depends on the amount of data you are
> working with, but it might be worth it to spin up a VM in the cloud on AWS,
> Azure, etc that has SQL Server on it and import the BCP files there. You
> could then export the data using the character format instead of the native
> format:
>
Man that really sucks but if it's the only way then I guess it's the only
way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-11-17 00:44:19 | Re: Adding a new module to postgres |
| Previous Message | Adrian Klaver | 2015-11-16 21:16:28 | Re: Importing directly from BCP files |