Re: [ODBC] linked tables in MS Access

Oh, I'm still feeling like a BFU :(

I'm using the last one version of odbc driver (08_02_0200) on Windows XP, 2000. Access is 2000 and 2003.

Of course I had commlog and mylog turned on. But I've never thought that writing some kb (ok, few megabytes) of text could have such big affect :(
When I was trying common windows odbc trace the disk worked very hard but postgres log didn't make full use of hard disk.

It seems that turning off helps very well. Access work by now commonly fast.

8000 rows query is prosessed in 0.8 s, see log:
2007-01-23 00:01:42 odbcuser SELECT LOG: 00000: duration: 813.000 ms statement: select * from osoby
It could be adequate I suppose. Postgres is on laptop.

I will try to change "use declare/fetch" and "cache size" but it is hard to debug via mylog because it is unbelievable slow.

And try to convert Access file to 2003 version further.

Thank you very much I haven't to forget to check logging settings.

Jirka

> ------------ Původní zpráva ------------
> Od: Ludek Finstrle <luf(at)pzkagis(dot)cz>
> Předmět: Re: [ODBC] linked tables in MS Access
> Datum: 23.1.2007 10:26:52
> ----------------------------------------
> > But I have MS Access front end containing linked tables to Postgres
> > via ODBC. And I'm struggling with slow performance. When I want to
> > open a table which contains about 8000 records it takes more then
> > 20 sec. When I want to move cursor at the last record it takes more
> > than 60 extra seconds.
> >
> > I've already checked Postgres server log and MS Access queries are
> > executed quickly (<500 ms).
> >
> > Is this normal behavior? Does MS Access cooperates with MS SQL such
> > better than with other DBMS via odbc?
>
> I see no description of your configuration.
> What's your ODBC settings? What ODBC driver do you use? What OS?
> I hope you haven't enabled the mylog output.
> How long takes it the psql to show 8000 records?
>
> BTW let's try play with "use declare/fetch" and "cache size" at first.
> And mylog output could help you to see where's the problem.
>
> Regards,
>
> Luf