Difference bet cube indexes and dso indexes

hi,
1.can any tell me the difference between cube indexes and dso indexes?
if we have aggregates on the cube it improves the performce of the query created on it
2.so why to create indexes on the cube?
for creating indexes on the dso i right click on dso and click create indexes
it is asking two options
1.unique key 2.non unique
4.what is the functionality of these two?
i will assign points if ur answers clear my questions

The BW automatically defines multiple indexes on your cubes, based on the dimensions you have defined. You do not need to create any additional indexes on your Fact tables. It can somtimes be helpful to create a secondary index on dimension tables or master data tables depending on their size and the queries. There is not BW wkbench tool to do this, it usually requires a DBA in most shops.
Secondary indexes on DSO/ODS can help some queries substantially, again, depending on the data and the queries. You can define secondary indexes on DSO/ODS from the BW workbench.
Aggregates are another tool for query performance, by summarizing the data, it can reduce the number of rows that must be read by a query. Again, it dpends on the query and the data as to how much an aggregate helps.

Similar Messages

Difference between primary eindex and secondary index?

hi experts
pls answer me
difference between primary eindex and secondary index?
rewads apply.
thanks.
naresh.

hi,
check this link.
http://help.sap.com/saphelp_47x200/helpdata/en/cf/21eb2d446011d189700000e8322d00/frameset.htm
A difference is made between Primary & Secondary indexes to a table. the primary index consists of the key fields of the table and a pointer to the non-keys-fields of the table. The Primary index is generated automatically when a table is created and is created in the datebase as the same times as the table. It is also possible to define further indexes to a table in the ABAP/4 dictionary, which are then referred to as Secondary indexes.
Always it is not mandatory that an index should have all the key fields of a table. To see the index of a table
goto SE11->specify table name->click on the indexes... button on the application toolbar.
Based on your requirement you can you any of those index fields in the where clause of your query. Always its a better practice to use the index fields in the order specified. While selecting the records from a table it is always better to select the fields in the same order as specified in the table.

Difference between unique constraint and unique index

1. What is the difference between unique constraint and unique index when unique constraint is always indexed ? Which one is better in this case for better performance ?
2. Is Composite index of 3 columns x,y,z better
or having independent/ seperate indexes on 3 columns x,y,z is better for better performance ?
3. It has been very confusing for me to decide which columns to index, I have indexed most foreignkey columns, is it a good idea ? We do lot of selects and DMLS on most of our tables. Is there any query that I can run and find out if indexes are really being used and if they are improving any performance. I have analyzed and computed my indexes using ANALYZE index index_name validate structure and COMPUTE STATISTICS;
null

1. Unique index is part of unique constraint. Of course you can create standalone unique index. But is is no point to skip the logical view of business if you spend same effort to achive.
You create unique const. Oracle create the unique index for you. You may specify index characteristic in unique constraint.
2. Depends. You can't utilize the composite index if the searching condition is not whole or front part of the indexing key. You can't utilize your index if you query the table for y=2. That is.
3. As old words in database arena, Index may be good or bad for a table depending on the size of table, number of columns in the table... etc. It is very environmental dependent. In fact, It is part of database nomalization. Statistic is a way oracle use to determine the execution plan.
Steve
null

Difference between sy-tabix and sy-index?

tell me about sy-tabix and sy-index?what is the difference between sy-tabix and sy-index?
Moderator Message: Please search before posting. Read the [Forum Rules Of Engagement |https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] for further details.
Edited by: Suhas Saha on Jun 18, 2011 5:33 PM

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

What is the difference between "Invisible" (11g) and "virtual" index?

Hi
What is the difference between the "Invisible" index and "virtual" index?
Thanks
Balaji

Indexes can be visible or invisible. An invisible index is maintained by DML operations and cannot be used by the optimizer. Actually takes space, but is not to be used as part of a potential access path.
AFAIK, a virtual index is created by the tools used in SQL statement access path tuning to provide an alternative for the optimizer to test. It does not take any real space as it is a pure in memory definition.

Difference between primary key and primary index

Dear All,
Hi... .Could you pls tell me the difference between primary key and primary index.
Thanks...

Hi,
Primary Key : It is one which makes an entry of the field unique.No two distinct rows in a table can have the same value (or combination of values) in those columns.
Eg: first entry is 111, if you again enter value 111 , it doesnot allow 111 again. similarly for the strings or characters or numc etc. Remember that for char or numc or string 'NAME' is not equal to 'name'.
Primary Index: this is related to the performance .A database index is a data structure that improves the speed of operations in a table. Indices can be created using one or more columns, providing the basis for both rapid random lookups and efficient ordering of access to records. The disk space required to store the index is typically less than the storage of the table (since indices usually contain only the key-fields according to which the table is to be arranged, and excludes all the other details in the table), yielding the possibility to store indices into memory from tables that would not fit into it. In a relational database an index is a copy of part of a table. Some databases extend the power of indexing by allowing indices to be created on functions or expressions. For example, an index could be created on upper(last_name), which would only store the uppercase versions of the last_name field in the index.
In a database , we may have a large number of records. At the time of retrieving data from the database based on a condition , it is a burden to the db server. so whenever we create a primary key , a primary index is automatically created by the system.
If you want to maintain indices on other fields which are frequently used in where condition then you can create secondary indices.
Reward points if helpful.
Thanks,
Sirisha..

Differences between function based index and normal index

Hi,
Please Give me some differences between function based index and normal indexes.
1. Is there any performance gain in function based index?
2. Why indexes created in DESC are treated as function based?
3. Every DESC index is b-tree index?
Thanks

check this link. This would give u a basic idea of what a function based index is .
http://www.oracle-base.com/articles/8i/FunctionBasedIndexes.php
--Prasad

CDS-18010 Error:A Index and a index with the same name

Hi
I am facing strange error is some one expert there to help me to get rid of this error.
CDS-18010 Error:A Index and a index with the same name 'LA_SP_FK_1' have been asked to be created.
I am generating tables from Data model diagram & getting this error.
Thanks,
Vijay

Your Right!!
Designer does not like 2 of the same name.
there are several bugs on the same name issue and CDS-18010
Bug.3973155/3443005 (92) CDS-18010 IN CAPTURING A TYPE WITH CONSTRUCTOR FUNTIONS IN ITS BODY:
Bug.2586582 (93) CDS-18010 A DOMAIN AND A DOMAIN WITH THE SAME NAME 'D1' BEEN ASKED TO CREATE:
Bug.2561625 (15) CDS-18010 GENERATION OF TWO SYNONYMS WITH SAME NAME BUT DIFFERENT SCOPE:
Bug.2072505 (93) CDS-18010 CAPTURING 2 TRIGGERS WITH SAME NAME ON ONE TABLE SHOULD BE A WARNING:
Bug.1689800 (90) CDS-18010 PLSQL WITH THE SAME PROCEDURE NAME ALREADY EXISTS:
Bug.1073311/1029997 (96) CDS-18010 ERROR ATTEMPTING TO CREATE 2 PROCEDURES WITH SAME NAME:
Just to name a few.
I would suggest you change the name.
Michael

What is difference bet call transaction and session method in BDC

hi
what is difference bet call transaction and session method in BDC
thanks.

Hi,
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
Thanks,
Reward If Helpful.

JTable SelectionModel - first Index and Las Index giving incorrect values

Hi Guys,
When i added a ListSelectionListener to the JTable's selectionModel, and tried to get the first index and last index values. The goofy thing i noticed is when you select different rows, the indexes are correct,but when you switch between the same rows, then indexes provided by the ListSelectionListener are always the same. Example : if you switch between 3 and 4 rows first index is 2 and last index is 3 which is correct, but if you go back 3rd row from 4th row, the first index is still 2 and last index is 3... which is kind of weird.
Any ideas about this, and why this is happenning.
I am pasting my sample code here any explanation is very helpfull to understand this behavior
Thanks
Nicedude
import javax.swing.JFrame;
import javax.swing.JPanel;
import javax.swing.JScrollPane;
import javax.swing.JTable;
import javax.swing.JComponent;
import javax.swing.ListSelectionModel;
import javax.swing.event.ListSelectionEvent;
import javax.swing.event.ListSelectionListener;
import java.awt.Dimension;
import java.awt.GridLayout;
import java.awt.event.MouseAdapter;
import java.awt.event.MouseEvent;
* SimpleTableSelectionDemo is just like SimpleTableDemo,
* except that it detects selections, printing information
* about the current selection to standard output.
public class SimpleTableSelectionDemo extends JPanel {
     private boolean DEBUG = false;
     private boolean ALLOW_COLUMN_SELECTION = false;
     private boolean ALLOW_ROW_SELECTION = true;
     public SimpleTableSelectionDemo() {
          super(new GridLayout(1,0));
          final String[] columnNames = {"First Name",
                    "Last Name",
                    "Sport",
                    "# of Years",
          "Vegetarian"};
          final Object[][] data = {
                    {"Mary", "Campione",
                         "Snowboarding", new Integer(5), new Boolean(false)},
                         {"Alison", "Huml",
                              "Rowing", new Integer(3), new Boolean(true)},
                              {"Kathy", "Walrath",
                                   "Knitting", new Integer(2), new Boolean(false)},
                                   {"Sharon", "Zakhour",
                                        "Speed reading", new Integer(20), new Boolean(true)},
                                        {"Philip", "Milne",
                                             "Pool", new Integer(10), new Boolean(false)}
          final JTable table = new JTable(data, columnNames);
          table.setPreferredScrollableViewportSize(new Dimension(500, 70));
          table.setSelectionMode(ListSelectionModel.SINGLE_SELECTION);
          if (ALLOW_ROW_SELECTION) { // true by default
               ListSelectionModel rowSM = table.getSelectionModel();
               rowSM.addListSelectionListener(new ListSelectionListener() {
                    public void valueChanged(ListSelectionEvent e) {
                         //Ignore extra messages.
                         if (e.getValueIsAdjusting()) return;
                         ListSelectionModel lsm = (ListSelectionModel)e.getSource();
                         if (lsm.isSelectionEmpty()) {
                              System.out.println("No rows are selected.");
                         } else {
                              int selectedRow = lsm.getMinSelectionIndex();
                         System.out.println("Row " + selectedRow + " is now selected.");
                              int first = e.getFirstIndex();
                                                        int last = e.getLastIndex();
                          System.out.println(" First Index is : " + first);
                          System.out.println(" Last Index is : " + last );
          } else {
               table.setRowSelectionAllowed(false);
          if (ALLOW_COLUMN_SELECTION) { // false by default
               if (ALLOW_ROW_SELECTION) {
                    //We allow both row and column selection, which
                    //implies that we *really* want to allow individual
                    //cell selection.
                    table.setCellSelectionEnabled(true);
               table.setColumnSelectionAllowed(true);
               ListSelectionModel colSM =
                    table.getColumnModel().getSelectionModel();
               colSM.addListSelectionListener(new ListSelectionListener() {
                    public void valueChanged(ListSelectionEvent e) {
                         //Ignore extra messages.
                         if (e.getValueIsAdjusting()) return;
                         ListSelectionModel lsm = (ListSelectionModel)e.getSource();
                         if (lsm.isSelectionEmpty()) {
                              System.out.println("No columns are selected.");
                         } else {
                              int selectedCol = lsm.getMinSelectionIndex();
                              System.out.println("Column " + selectedCol
                                        + " is now selected.");
          if (DEBUG) {
               table.addMouseListener(new MouseAdapter() {
                    public void mouseClicked(MouseEvent e) {
                         printDebugData(table);
          //Create the scroll pane and add the table to it.
          JScrollPane scrollPane = new JScrollPane(table);
          //Add the scroll pane to this panel.
          add(scrollPane);
     private void printDebugData(JTable table) {
          int numRows = table.getRowCount();
          int numCols = table.getColumnCount();
          javax.swing.table.TableModel model = table.getModel();
          System.out.println("Value of data: ");
          for (int i=0; i < numRows; i++) {
               System.out.print("    row " + i + ":");
               for (int j=0; j < numCols; j++) {
                    System.out.print(" " + model.getValueAt(i, j));
               System.out.println();
          System.out.println("--------------------------");
      * Create the GUI and show it. For thread safety,
      * this method should be invoked from the
      * event-dispatching thread.
     private static void createAndShowGUI() {
          //Make sure we have nice window decorations.
          JFrame.setDefaultLookAndFeelDecorated(true);
          //Create and set up the window.
          JFrame frame = new JFrame("SimpleTableSelectionDemo");
          frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
          //Create and set up the content pane.
          SimpleTableSelectionDemo newContentPane = new SimpleTableSelectionDemo();
          newContentPane.setOpaque(true); //content panes must be opaque
          frame.setContentPane(newContentPane);
          //Display the window.
          frame.pack();
          frame.setVisible(true);
     public static void main(String[] args) {
          //Schedule a job for the event-dispatching thread:
          //creating and showing this application's GUI.
          javax.swing.SwingUtilities.invokeLater(new Runnable() {
               public void run() {
                    createAndShowGUI();
}

>
I was (maybe wrongly) under the impression that, last index will give the last selected value and first index will give me the currect selected value. Not maybe - your impression sure is wrong. Honestly can't understand how it's possible to mis-interpret the api doc of ListSelectionEvent (except not reading it ;-)
"Represents a change in selection status between firstIndex and
lastIndex, inclusive. firstIndex is less than or equal to
lastIndex. The selection of at least one index within the range will
have changed."
Jeanette

How get column index and row index in gridpane of javafx

how get column index and row index in gridpane of javafx. see the code below
Text text1 = new Text("Text 1");
Text text2 = new Text("Text 2");
StackPane root = new StackPane();
GridPane gridPane = new GridPane();
gridPane.add(text1, 0, 0);
gridPane.add(text2, 1, 0);
When Mouse Entered On text1 i want to get the column index and row index of GridPane
text1.setOnMouseEntered(new EventHandler<MouseEvent>() {
            @Override
            public void handle(MouseEvent e) {
                //want to get column index =0 and row index=0
Please let me know.

Hi,
If I remember well:
[code]
text1.setOnMouseEntered(new EventHandler<MouseEvent>() {
            @Override
            public void handle(MouseEvent e) {
                //want to get column index =0 and row index=0
                System.out.println("Column: " + GridPane.getColumnIndex(text1));
[/code]
-- daniel

What is difference between sy-tabix and sy-index.

SAP Seniors,
Can you please let me know what is difference between sy-index and sy-tabix.
I read the SAP help, it is confusing for me. it looks like both are same from help. please help me.
Thank you
Anitha.

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

What is the difference between the drop and create the index and rebuild index ?

Hi All,
what is the difference between drop and create index & rebuild index ? i think both are same...Please clarify if both are same or any difference...
Thanks in Advance,
rup

Both are same. Rebuilding an index drops and re-creates the index.
Ref:
SSMS - https://technet.microsoft.com/en-us/library/ms187874(v=sql.105).aspx
TSQL - https://msdn.microsoft.com/en-us/library/ms188388.aspx
I would suggest you to also refer one of the best index maintenance script as below:
https://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html

Difference between btree index and bitmap index

i knw btree is the default index.but what's are the other difference present.

21 characters and 10 seconds at google:
http://www.akadia.com/services/ora_bitmapped_index.html
http://www.oracle.com/technology/pub/articles/sharma_indexes.html
http://www.dba-oracle.com/art_9i_indexing.htm
Dim

Access path difference between Primary Key and Unique Index

Hi All,
Is there any specific way the oracle optimizer treats Primary key and Unique index differently?
Oracle Version
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> Sample test data for Normal Index
SQL> create table t_test_tab(col1 number, col2 number, col3 varchar2(12));
Table created.
SQL> create sequence seq_t_test_tab start with 1 increment by 1 ;
Sequence created.
SQL> insert into t_test_tab select seq_t_test_tab.nextval, round(dbms_random.value(1,999)) , 'B'||round(dbms_random.value(1,50))||'A' from dual connect by level < 100000;
99999 rows created.
SQL> commit;
Commit complete.
SQL> exec dbms_stats.gather_table_stats(USER_OWNER','T_TEST_TAB',cascade => true);
PL/SQL procedure successfully completed.
SQL> select col1 from t_test_tab;
99999 rows selected.
Execution Plan
Plan hash value: 1565504962
| Id | Operation         | Name       | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |            | 99999 |   488K|    74   (3)| 00:00:01 |
|   1 | TABLE ACCESS FULL| T_TEST_TAB | 99999 |   488K|    74   (3)| 00:00:01 |
Statistics
          1 recursive calls
          0 db block gets
       6915 consistent gets
        259 physical reads
          0 redo size
    1829388 bytes sent via SQL*Net to client
      73850 bytes received via SQL*Net from client
       6668 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
      99999 rows processed
SQL> create index idx_t_test_tab on t_test_tab(col1);
Index created.
SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB',cascade => true);
PL/SQL procedure successfully completed.
SQL> select col1 from t_test_tab;
99999 rows selected.
Execution Plan
Plan hash value: 1565504962
| Id | Operation         | Name       | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |            | 99999 |   488K|    74   (3)| 00:00:01 |
|   1 | TABLE ACCESS FULL| T_TEST_TAB | 99999 |   488K|    74   (3)| 00:00:01 |
Statistics
          1 recursive calls
          0 db block gets
       6915 consistent gets
          0 physical reads
          0 redo size
    1829388 bytes sent via SQL*Net to client
      73850 bytes received via SQL*Net from client
       6668 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
      99999 rows processed
SQL> Sample test data when using Primary Key
SQL> create table t_test_tab1(col1 number, col2 number, col3 varchar2(12));
Table created.
SQL> create sequence seq_t_test_tab1 start with 1 increment by 1 ;
Sequence created.
SQL> insert into t_test_tab1 select seq_t_test_tab1.nextval, round(dbms_random.value(1,999)) , 'B'||round(dbms_random.value(1,50))||'A' from dual connect by level < 100000;
99999 rows created.
SQL> commit;
Commit complete.
SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB1',cascade => true);
PL/SQL procedure successfully completed.
SQL> select col1 from t_test_tab1;
99999 rows selected.
Execution Plan
Plan hash value: 1727568366
| Id | Operation         | Name        | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |             | 99999 |   488K|    74   (3)| 00:00:01 |
|   1 | TABLE ACCESS FULL| T_TEST_TAB1 | 99999 |   488K|    74   (3)| 00:00:01 |
Statistics
          1 recursive calls
          0 db block gets
       6915 consistent gets
          0 physical reads
          0 redo size
    1829388 bytes sent via SQL*Net to client
      73850 bytes received via SQL*Net from client
       6668 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
      99999 rows processed
SQL> alter table t_test_tab1 add constraint pk_t_test_tab1 primary key (col1);
Table altered.
SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB1',cascade => true);
PL/SQL procedure successfully completed.
SQL> select col1 from t_test_tab1;
99999 rows selected.
Execution Plan
Plan hash value: 2995826579
| Id | Operation            | Name           | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT     |                | 99999 |   488K|    59   (2)| 00:00:01 |
|   1 | INDEX FAST FULL SCAN| PK_T_TEST_TAB1 | 99999 |   488K|    59   (2)| 00:00:01 |
Statistics
          1 recursive calls
          0 db block gets
       6867 consistent gets
          0 physical reads
          0 redo size
    1829388 bytes sent via SQL*Net to client
      73850 bytes received via SQL*Net from client
       6668 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
      99999 rows processed
SQL> If you see here the even though statistics were gathered,
     * In the 1st table T_TEST_TAB, the table is still using FULL table access after creation of index.
     * And in the 2nd table T_TEST_TAB1, table is using PRIMARY KEY as expected.
Any comments ??
Regards,
BPat

Thanks.
Yes, ignored the NOT NULL part.Did a test and now it is working as expected
SQL> create table t_test_tab(col1 number not null, col2 number, col3 varchar2(12));
Table created.
SQL>
create sequence seq_t_test_tab start with 1 increment by 1 ;SQL>
Sequence created.
SQL> insert into t_test_tab select seq_t_test_tab.nextval, round(dbms_random.value(1,999)) , 'B'||round(dbms_random.value(1,50))||'A' from dual connect by level < 100000;
99999 rows created.
SQL> commit;
Commit complete.
SQL> exec dbms_stats.gather_table_stats('GREP_OWNER','T_TEST_TAB',cascade => true);
PL/SQL procedure successfully completed.
SQL> set autotrace traceonly
SQL> select col1 from t_test_tab;
99999 rows selected.
Execution Plan
Plan hash value: 1565504962
| Id | Operation         | Name       | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |            | 99999 |   488K|    74   (3)| 00:00:01 |
|   1 | TABLE ACCESS FULL| T_TEST_TAB | 99999 |   488K|    74   (3)| 00:00:01 |
Statistics
          1 recursive calls
          0 db block gets
       6912 consistent gets
          0 physical reads
          0 redo size
    1829388 bytes sent via SQL*Net to client
      73850 bytes received via SQL*Net from client
       6668 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
      99999 rows processed
SQL> create index idx_t_test_tab on t_test_tab(col1);
Index created.
SQL> exec dbms_stats.gather_table_stats('GREP_OWNER','T_TEST_TAB',cascade => true);
PL/SQL procedure successfully completed.
SQL> select col1 from t_test_tab;
99999 rows selected.
Execution Plan
Plan hash value: 4115006285
| Id | Operation            | Name           | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT     |                | 99999 |   488K|    63   (2)| 00:00:01 |
|   1 | INDEX FAST FULL SCAN| IDX_T_TEST_TAB | 99999 |   488K|    63   (2)| 00:00:01 |
Statistics
          1 recursive calls
          0 db block gets
       6881 consistent gets
          0 physical reads
          0 redo size
    1829388 bytes sent via SQL*Net to client
      73850 bytes received via SQL*Net from client
       6668 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
      99999 rows processed
SQL>

Difference bet cube indexes and dso indexes

Similar Messages

Maybe you are looking for