🚀 go-pugleaf

In article <3497443D.2D58B827@hotmail.com>, rfath@hotmail.com says...
> The new query designer keeps hanging when I choose a remote table from
> the SQL designer. I am connecting to Sybase and DB2 with ODBC drivers. I
> can view the tables from the navigator with no problems. It always
> "hangs,  hour glass" on large tables with many fields. Smaller tables
> seem to work but take a long time to load? Any thoughts this
> is a real show stopper for me?
> 
Is this a true 'hang' or just very slow performance?  I suspect you are 
simply seeing slow delivery of query results, as you also report poor 
performance with smaller tables.

Try to locate the bottleneck.  Likely target areas will be the capacity 
of the network to transmit the selected records, and the performance of 
the server when actually picking the records.

Check how much load is actually on the server, and try to get a handle 
on its true capability.  You may be competing with other users, and 
possibly other network services on the same machine.  I know it is 
possible to load a database server engine on the same host that provides 
web, ftp, print, and file services, but something will give under the 
load unless you have an obscene amount of memory and multiple fast 
processors.

If the server is NT check it is configured for memory allocation as 
_application_ server, not file server.  This can make a major difference 
to performance.

All your table types are supported by the latest 32-bit SQL Links. Try 
using the native drivers instead of the notoriously slow ODBC.

-- 
Paul Franks (TeamB)

pfranks@globalnet.co.uk
74431.265@compuserve.com