GeekInterview.com
  I am new, Sign me up!
 
GeekInterview.com  >  Interview Questions  >  Oracle  >  SQL
Go To First  |  Previous Question  |  Next Question 
 SQL  |  Question 94 of 171    Print  
on index
why u need indexing ? where that is stroed
and what u mean by schema object?
for what purpose we are using view

  
Total Answers and Comments: 3 Last Update: July 14, 2009     Asked by: basukolur014 
  
 Sponsored Links

 
 Best Rated Answer

No best answer available. Please pick the good answer available or submit your answer.
August 15, 2006 03:38:08   #1  
Rama Krishna        

RE: on index why u need indexing ? where that is...
Friend!! We cant create an Index on Index.. Index is stoed in user_index table.Every object that has been created on Schema is Schema Object like Table View etc.If we want to share the particular data to various users we have to use the virtual table for the Base table...So tht is a view..Thanks&RegdsRama Krishna TCSHyd
 
Is this answer useful? Yes | No
October 09, 2006 08:30:35   #2  
SateeshReddy Member Since: October 2006   Contribution: 1    

RE: on index why u need indexing ? where that is...

Hello frnd

why cant we create an index on the index....i think according to the database concepts we can create it. it may called as multilevel indexes...like B trees and B+trees are examples for that....

we need this type of index is due to if the index size is also too large we can go with index for that index....

Sateesh Reddy


 
Is this answer useful? Yes | No
July 14, 2009 02:12:54   #3  
jaspreet.nagra Member Since: July 2009   Contribution: 3    

RE: on index why u need indexing ? where that is stroed and what u mean by schema object?for what purpose we are using view
Sometime the special index you get automatically with every primary key and unique constraint might not help in certain situations. If this happens then maybe it's time to explicitly create a second index on the primary key.

An explicit index can help when the structure of the automatic index is all wrong; e.g. when the columns are placed in the wrong order for certain sorting or searching criteria or the default ASC sort sequence in a multi-column primary key doesn't help with a particular ORDER BY clause.

Another situation where an explicit index might help is when a huge number of child table rows exist for each parent row. A large "fan-out" from primary-to-foreign key values can cause the special primary-and-foreign-key index to grow fat and slow. For example if there are 1000 rows in a child table for every parent row then a query based on the primary key must deal with 1000 index entries for every different primary key value.

If you read the concept of Mutlileve Indexing it doesn;t tell to create index on index instead it says to create index at another level. So in above mentioned 2 examples implicit index created on creation of Primary Key will be at 2nd level and the explicit unique index created will be at 1st level.

 
Is this answer useful? Yes | No


 
Go To Top


 Sponsored Links

 
About Us -  Privacy Policy -  Terms and Conditions -  Contact -  Ask Question -  Propose Category -  Site Updates 

Copyright © 2005 - 2009 GeekInterview.com. All Rights Reserved

Page copy protected against web site content infringement by Copyscape