Re: Application bottlenecks

Hi Merlin...

We have an application that he uses one extfh that was modified by us
so that it has access Oracle bases natively through the use of
ProCobol. I am interested in its work, would like to get greaters
information.

We use Microfocus NetExpress 3.0.

Cleber.

2005/9/8, Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>:
> Hi Carlos, I am working on project right now you might be interested in, namely a extfh interface to postgresql and a isam wrapper for libpq. I already have an isam bridge working direct to postgresql from AcuCobol without using odbc or a commercial driver. I just need to convert it to extfh and do a few other things to support microfocus.
>
> Merlin
>
> ________________________________________
> From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Carlos Henrique Reimer
> Sent: Wednesday, September 07, 2005 7:24 AM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] Application bottlenecks
>
> Hello,
>
> We are using Cobol Microfocus and pgsqlODBC to access Postgresql.
>
> Originally these applications only accessed Oracle databases without ODBC, only Procobol and now we´re migrating to Postgresql and ODBC. The application logic doesn´t changed, but some applications have higher response times than the Oracle version. We worked on database tunning but even so, the response times are very different.
>
> I turned on logging sql statemants in the server (log_duration) and discovered that the sum of all SQL duration times gives only 30% of the total response time felt at the client. This gives me a suspect that the bottleneck is outside the server.
>
> Am I in the right way?
>
> How can I discover the SQL duration times at the client? Is there some tool I could use?
>
> Thanks in advance!
>
> Reimer
> ________________________________________
> Yahoo! Messenger com voz: PROMOÇÃO VOCÊ PODE LEVAR UMA VIAGEM NA CONVERSA. Participe!
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>

--
Cleber Nardelli
IPM Automação e Consultoria
9998-8670