To Robert Freeman, Thank You so much, I am pointing to Newbie DBAs/Immediate DBAs Tasks, What can they do to improve performance on Database by doing something with TABLEs/INDEXs. Maybe, They can improve performance database since created tablespaces, created tables. I know We can read on Oracle Docs and Books. But I hope some tricks and ideas . Thank You Surachart Opun Oracle ACE, Contributor (Oracle User Group in Thailand) http://surachartopun.com skye: surachart_op On Sat, Mar 19, 2011 at 9:04 PM, Robert Freeman <robertgfreeman@xxxxxxxxx>wrote: > Exadata has additional forms of compression available in HCC that go even > beyond the OLTP compression. For performance the lighter form of HCC > compression (warehouse compression) might well be what you want to look at. > With a significant reduction in rows per block, combined with the rest of > Exadata's storage cell features, you can get some incredible performance. > > Here is a white paper on Exadata HCC: > http://www.oracle.com/technetwork/middleware/bi-foundation/ehcc-twp-131254.pdf > > Cheers! > > Robert G. Freeman > Master Principal Consultant, Oracle Corporation, Oracle ACE > Author of various books on RMAN, New Features and this shorter signature > line. > Blog: http://robertgfreeman.blogspot.com > > > ------------------------------ > *From:* Surachart Opun <surachart@xxxxxxxxx> > *To:* Subodh Deshpande <deshpande.subodh@xxxxxxxxx> > *Cc:* "Oracle-L@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx> > *Sent:* Sat, March 19, 2011 2:27:06 AM > *Subject:* Re: What is Your Idea for optimizing Table Performance? > > Thank You. Good idea for table types. that is something what we should > decide before create table. > Example: use varchar2 not varchar/use number when business need number.... > Perhaps, We should know about data... On new 11G, Compression is good for > DW. How do you think? > > On 11gR2, Database Smart Flash Cache, this may good for OLTP. If we talk > about Exadata, we will use "Exadata Smart Flash Cache" > > and your idea? > > Thank You > Surachart Opun > Oracle ACE, Contributor (Oracle User Group in Thailand) > http://surachartopun.com > skye: surachart_op > > > > > On Sat, Mar 19, 2011 at 12:47 PM, Subodh Deshpande < > deshpande.subodh@xxxxxxxxx> wrote: > >> I think tables and their types should be decided beofre creating it.. >> the first column of the table is usually a primary key because of its >> uniqueness..where as rest of the columns gives more information of the >> primary key or about other columns in the tables.. >> >> the factor 'searching of information on some basis' decides indexes >> >> grouping of tables, indexes, tablespaces, datafiles is usaully from the >> application, performance, usuages, minimum affordable downtime and hence >> maintenance point of view (insightful architect and dba can recommend >> hardware requirement using this info) ..here there is scope for giving added >> redundanct and it should be allowed only from maintenance and performance >> point of view and that too if certain objects will have hardly some growth. >> >> architect should recommend (if he/she knows dba tasks) backup recovery and >> performance gain practices(including table performance, index performance >> etc) or should decide with dba how to proceed about depending upon the >> availabilty of man power and dba tasks at client side.. >> >> nomination of objects such as tables, indexex, tablespaces, datafiles >> should give easyness in understanding of these things to a dba, developer >> and or maintenance technician >> >> these are my view points considering a general ERP kind of application >> >> thanks..subodh >> On 18 March 2011 16:43, Surachart Opun <surachart@xxxxxxxxx> wrote: >> >>> When we work with Oracle Database as DBA or Developer. We have to >>> maintain about table segments. We have to know about Tablepsace/Database >>> file. >>> When we create table, Do you think about it before? Or Do something after >>> created table? >>> >>> What is Your Idea for optimizing Table Performance? >>> >>> Surachart Opun >>> http://surachartopun.com >>> skye: surachart_op >>> >>> >>> >> >> >> -- >> ============================== >> DO NOT FORGET TO SMILE TODAY >> ============================== >> > >