commentBlock = $("#comment_post_32846").find('.comment-blocks'); commentBlock.find('.loading').hide(); commentBlock.find('.see-all-comments').hide(); commentBlock.html("
<\/a>
\"it_user3309<\/a>
it_user3309<\/a>Presenter at a consultancy<\/span><\/div>
<\/span>Consultant<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Arup -- I agree don\'t go too wild applies to anything. However, people read these things about Exadata and go wild OR just do nothing so as to keep everything the same. And not many people talk about Oracle Text Indexes and how different the behaviour.<\/p>\n\n

Also in your \"travels on Exadata\" have you seen any effect of gathering system statistics with the \'EXADATA\' parameter? <\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user238071<\/a>
it_user238071<\/a>Principal Global Database Architect at a leisure / travel company with 1,001-5,000 employees<\/span><\/div>
<\/span>Vendor<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Amin - thank you for the comments. Your \"Don\'t go too wild with dropping indexes\" comment applies to any advice, anywhere. Dropping indexes is not the primary objective of Exadata. And I never actually said that. What I said was that Exadata allows us to perform full table scans more effectively, which was not possible earlier. That is not the same thing as dropping existing indexes which may have been created for entirely different reasons, e.g. to enforce integrity constraints.<\/p><\/div>