From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | Afewtips(dot)com <afewtips(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Connect to SQL Server via ODBC from Postgresql |
Date: | 2008-01-10 14:54:07 |
Message-ID: | b42b73150801100654t55873bbkc517752710d5cbdc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jan 4, 2008 11:51 AM, Afewtips.com <afewtips(at)gmail(dot)com> wrote:
> > I do read mentions about dblink connections, but how to install it
> > looks unclear and complicated.
> >
small clarification here. dblink is for connecting two postgresql
databases together. It is, IMO, neither unclear nor complicated :-).
dbilink, (note the 'I'), which aiui uses perl dbi in a dblink style
interface...never used it personally.
for moving data in and out of sql server and postgresql, you have a
number of options, odbc, dbi, php, etc etc. in the end, you have to
query a, process the result and send the answer to b.
csv format is great for data transfers in and out of postgres. for
example, you can pull data out of something in csv, load it into a
postgresql scratch table with the copy statement, and run queries
there to get it into the final destination table.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-01-10 14:54:29 | Re: 8.3 Beta Incompatible Data Disaster |
Previous Message | Erik Jones | 2008-01-10 14:52:11 | Re: vacuum, dead rows, usual solutions didn't help |