On 10/21/06, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> Carlo Stonebanks wrote:
> > Our Windows-based db server has to integrate with users that work regularily
> > with Access.When attempting to import user's data from Access MDB files to
> > PostgreSQL, we try on eof two things: either import using EMS SQL Manager's
> > Data Import from Access utility, or export from Access to Postgresql via an
> > odbc-based connectionin both cases, the performance is just awful.
> > Performance with Tcl's native postgres driver seems rather fine running from
> > Windows a Windows client, BTW.
> >
> > ODBC is often blamed for this sort of thing - I have the 8.01.02 release
> > dated 2006.01.31. Everything appears to be at its default setting.
>
> Try Command Prompt's ODBC driver. Lately it has been measured to be
> consistently faster than psqlODBC.
>
> http://projects.commandprompt.com/public/odbcng
just curious: what was the reasoning to reimplement the protocol stack
in odbcng? the mainline odbc driver went in the other direction.
carlo: please, please, get your mail server to quit telling me your
mailbox is full :)
merlin
