D
dbeavon
Guest
There is now an article that describes the problem with QUERY-PREPARE in a client-server environment (even where the entire database schema is cached locally: knowledgebase.progress.com/.../QUERY-PREPARE-generates-excessive-network-traffic Unfortunately the QUERY-PREPARE does an excessive amount of work over the network. This work - which is done while preparing the query - ends up costing more than the work of actually gathering the customer data. It does not seem that QUERY-PREPARE would need the remote schema if it is already cached locally. IE. The QUERY-PREPARE shouldn't need to get the remote schema one time, let alone doing it repeatedly for every single predicate ( Customer.CustNum = 1234).
Continue reading...
Continue reading...