×
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.
i'm with Brian on this one. write(e) is much less painful and a heckuva
lot less I/O intensive i would think. another alternative would be using
SQL to process the data, just select where not in (select 1 from previous)
yada yada...
Thanks,
Tommy Holden
From: BMay@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 06/15/2010 02:34 PM
Subject: RE: System slow-down - disk usage?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
I would still try it with the write and catch method. Even though you may
have 40% dups on occasion and job log entries to remove, it may still be
faster than checking the huge previous table on every incoming
transaction.
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
