> It's hot here. I wish I was at the beach and I feel like an ant. Hmmm.
> During an indexed query on a single table the index will be > accessed, then the table, then the index,then the table, > then the index,then the table then the index,then the table. Assuming you get 4 rows returned :) > If the index and the table are on the same disk then a lot of > time will be taken up by head seek movement. > If they are on the different disks then the "index" heads can > locate their data and stay there - and the "data" heads can > locate their data and stay there. Less head movement, less wasted time. I would understand this if I had one index and one table. On a busy system with many users wouldn't the heads move, anyway, to serve queries that used other indexes and tables? Gudmundur -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Gudmundur Bjarni Josepsson INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
