|
<snip>
1) I can replace our 'overall-logcal files' with SQL Views, but I
cannot
create an index over multiple tables (as I can via a logical file),
so these views will not give me the sub-second accesstimes I have now
(or am
I wrong in this?)
2) Hibernate creates "joins" over multiple tables under the covers, but
-as
far as I know- this cannot be done on the current "overall-logcial
files",
or on any alternative using "union"- views (I hope I am wrong on this
one
too) ?
</snip>
I am not sure this answers the question. The question was if you run
this over one region using SQL, how long does it take to return the
result set and how big is the result set?
For example, if it takes 30 minutes to query one region and it returns a
100,000 records, union might not be practical.
If it takes a second to run and returns a single result set, unions
should work fine.
Based on what you are saying, you would like to run this from a PC
application. Why not build the result in a stored procedure and return
to caller or am I missing something?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.