×
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.
So the UNIQUE was a good one in this case. I think it would be fair to
say that for files of this genre, in which there should be no duplicate
keys, then it should be a good one in all of that genre. Unless you can
come up with a good business reason why not, and can give a sample
thereof.
On that constraint... I am going with what Elvis said and that was the
read/write balance thing. Although I will grant you, that I would think
that would be more applicable in other issues, like validating that a
field is truly numeric, kind of stuff. As most know, DDS speeds up the
writes and slows down the reads and allows character data in the numerics.
SQL slows down the writes by making sure that there is no character data
in the numerics but speeds up the reads.
Rob Berendt
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
