|
I am coming into this conversation very late but I would like to throw in some thoughts on system aspects of the to I/O's methods. Native I/O absolutely requires Logical Views in order to operate in any reasonable fashion. Logical Views require system resources to maintain them even if it is distributed through concurrent time. SQL will work without indexes or view but operates like cold molasses running up hill. Indexes also require system resources to maintain the indexes and fine tuning of the optimized to make sure that run time objects make use of them. Now we have to add on the basic operational requirement of the function. Is it a heads down pounder or is an occasional inquiry/update function. Reviewing these items, in my mind's eye and experience I come up with a SWAG. Use native I/O for the pounders and, and if there is not a logical view defined for exactly what you need for the light weight inquiry/update functional requirements. Regardless of the final conclusions on betterness, it certainly nice to have both tools in our toolbox. Jack Derham Direct Systems, Inc. Marietta, GA 30068
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.