×
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.
...lack thereof, actually. It's really slow--does DSPJRN know something
SQL doesn't? Or is it me?
DSPJRN inserts 300,000 records from the current receiver into a file in 10
seconds while the same task in SQL drags for 40 seconds or more before any
(a few hundred) results are available. The journaled files are extremely
busy, with the majority of the transactions (writes, a gazillion updates)
against today's orders. The journal receiver is 2.5 GB with about
10,000,000 entries (lots of journaled access paths). I have not
benchmarked the QjoRetrieveJournalEntries API.
Do we pay a performance penalty for the convenience of SQL access? I'm
grateful for any suggestions that will improve performance (mine or the
code's).
This mailing list archive is Copyright 1997-2025 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.