SQL, Logical Files, Unions & Indexes. -- MIDRANGE-L

Amazing how much fine detail there is in this stuff. I purposely put upthose key words, knowing it would capture the eye of those I know arecurious and willing to share their knowledge.

This is a finance application in Australia which is 25 years old. Theapplication is built around 5 'states'. Twenty five years ago theappropriate library at the top of the library list allowed the state officesto work with their own data.

We now have a centralized settlement process whereby loans which need to beauithorised by a human (as opposed to the auto approval ) are routed. A loanauthorization officer handles loan applications from all of the states andthey are presented in a 'work-basket' by the SQL I am trying to optimize ona first in first out basis.. In other words the SQL uses a UNION to applythe same select criteria to each file in each of the libraries. In otherwords, their work queue is Australia wide, and not state based.

We could change their work practices to become state based, but this addscomplexity and defeats the concept of a universal queue.

I'm at home at the moment and don't have the SQL at hand, but when I get towork I'll publish it.

I find this debate very imformative as it elicits all the subtleties of thisgrey world of DDS & DDL overlap.

What do people think of having an SQL only list to concentrate theknowledge?

I agree that with IBM that DBA on a small site is uunecesssary, but on abig site I think that it should be compulsory. There is no way that theaverage developer can be cognizant of all the intricasies of tuning. I'mjust starting to immerse myself, and the water seems to be extremely deepand full of sharks!



Thanks for all your contributions.





Regards, Mike Pantzopoulos

_________________________________________________________________

Join the millions of Australians using Live Search. Try live.com.auhttp://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=740&referral=million&URL=http://live.com.au