Re: Performance question and SQL SERVER -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 29 May 2013 13:10, Peter Connell wrote:

Tried that. DEBUG shows that the ODP is deleted as soon as you SQL
delete the records.

The /fastdelete/ feature will effectively DROP the TABLE just like how one might DROP and CREATE of a work file. Avoid or disable [as I recall, there is an INI option\setting] that fast-delete feature for that DELETE request, if the change from DROP\CREATE to using DELETE effected the same loss of re-use.

I intend to try JDBCR4.

By shifting from the current purely dynamic requests to another purely dynamic interface, I would not expect to see much difference.

<<SNIP>>

Regards, Chuck

Gary Thompson on Thursday, 30 May 2013 7:56 a.m. wrote:

maybe try:
instead of a new work file try same file but use SQL to delete all
rows so you just load/clear/load/clear etc also any suggestions
from System i Navigator index advisor ?

Peter Connell on Wednesday, May 29, 2013 1:48 PM wrote:

<<SNIP>> when a new work file is created for the next client
transaction, these ODPs get deleted and the transaction is slow
again. <<SNIP>>

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.