Re: poor performance on ACCESS 97 client/oracle 7.3 server application

From: <kaiserrj_at_my-deja.com>
Date: Mon, 14 Jun 1999 12:19:00 GMT
Message-ID: <7k2rve$ndq$1_at_nnrp1.deja.com>


Hey!

Just a thought, saw this when I was doing a zip code thing. My sql converted the table's zip-code to char - to match the client's case. The fastest time I could manage was 23 seconds. Changed things around and converted the client's value to number (matching the table's case) and got 2 second response.

So, generally, your sql may need to be optimized.

Otherwise, Oracle's OO4OLE (oracle objects for OLE) have a reputation as being faster than MS ODBC drivers, and drivers produced by Intersolve are super fast. You'd definately benefit by testing a base-line installation with different drivers just to measure their effect.

Good luck, and post this to the access newsgroup and you'll get lots of stuff in response (it's a regular topic there).

Later, Rich

Disclaim: This is not my company's stuff.

In article <3764e3c9.8131011_at_news.neckar-alb.de>,   brosenau_at_gss-online.de (Bernd Rosenau) wrote:
> Hi,
>
> our ACCESS 97 client/oracle 7.3 application has poor performance
> despite ORACLE running on a powerfull unix machine with lots of memory
> (several hundred MB !)
>
> The machines on the client side are also very well equiped
> (400 MHZ Pentium II machines with 128 MB of RAM)
>
> Very little data is stored in tables (less than 1000 rows in each
> table !!)
>
> Could it be the case that the NETWARE client installed on these
> machines slows database access down ?
>
> We had a simliar effect at a different client where our ACCESS 97 app
> is run with SQL Server at back end.
>
> Many thanks in advance for your help,
>
> Cheers, Bernd.
>
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Mon Jun 14 1999 - 14:19:00 CEST

Original text of this message