SQL*NET over a Wide Area Network
From: Steve Bellamy <100074.1541_at_compuserve.com>
Date: Tue, 01 Dec 1998 19:34:59 -0500
Message-ID: <01be1d8a$9682cf00$351bd3d4_at_adhoc>
[Quoted] The application that I'm working on operates fine over a LAN (even old 4 or10 mbps links), but we are having performance problems at locations connecting over slow WAN or dial up links. The 64K links seem to be able to carry the necessary bandwidth, but not the volumn of small (<2K) packets generated by SQL*NET. Where possible I've tuned the OO4O dynaset options to maximise the data retrieved by each fetch, but the application generates many selects to get unrelated data from various tables.
For example, one form makes five independant selects which each return 0-20 rows. It takes 2 seconds to load the form when the data is retrieved over the LAN, but 5 seconds over the WAN.
Date: Tue, 01 Dec 1998 19:34:59 -0500
Message-ID: <01be1d8a$9682cf00$351bd3d4_at_adhoc>
[Quoted] The application that I'm working on operates fine over a LAN (even old 4 or10 mbps links), but we are having performance problems at locations connecting over slow WAN or dial up links. The 64K links seem to be able to carry the necessary bandwidth, but not the volumn of small (<2K) packets generated by SQL*NET. Where possible I've tuned the OO4O dynaset options to maximise the data retrieved by each fetch, but the application generates many selects to get unrelated data from various tables.
For example, one form makes five independant selects which each return 0-20 rows. It takes 2 seconds to load the form when the data is retrieved over the LAN, but 5 seconds over the WAN.
Any ideas would be appreciated!
Steve Bellamy Received on Wed Dec 02 1998 - 01:34:59 CET