<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: secondry indexes in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814265#M658022</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hI &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;econdary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The database optimizer decides which index on the table should be used by the database to access data records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Oct 2007 07:12:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-04T07:12:07Z</dc:date>
    <item>
      <title>secondry indexes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814260#M658017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what will happen when we create secondary index. why don't we create more than 5 secondary indexes and how the system will(the flow) search for records after creating an index.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Oct 2007 06:47:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814260#M658017</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-04T06:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: secondry indexes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814261#M658018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check the belwo links on secondary indexes..&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb20446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb20446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb47446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb47446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nagaraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Oct 2007 06:51:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814261#M658018</guid>
      <dc:creator>former_member404244</dc:creator>
      <dc:date>2007-10-04T06:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: secondry indexes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814262#M658019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dharani,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Primary indexes are existing indexes we can use directly those indexes. we need to create the secondary indexes. In tables we will use both primary and secondary indexes.&lt;/P&gt;&lt;P&gt;Create secondary indexes step by step procedure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Secondary index is created to enhance the performance. If you create wrongly defined index, it will decreases the performance.&lt;/P&gt;&lt;P&gt;Follow the below steps to create secondary index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A.Go to t_code (se11) display your table name.&lt;/P&gt;&lt;P&gt;B.To create new index, click on index button on tool bar.&lt;/P&gt;&lt;P&gt;C.Give the index name.&lt;/P&gt;&lt;P&gt;D.Pass short text description for your index.&lt;/P&gt;&lt;P&gt;E.Bottom of the table pass field names on which you want index.&lt;/P&gt;&lt;P&gt;F.Save and activate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. You can create up to 16 indexes. But 5 is recommended...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Harini.S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Oct 2007 07:06:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814262#M658019</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-04T07:06:13Z</dc:date>
    </item>
    <item>
      <title>Re: secondry indexes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814263#M658020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It is not advisable to cretae a Secondary index unless the Performance is very poor , killing time.&lt;/P&gt;&lt;P&gt;It is not good to cretae Secondary index b'coz it will increase the LOAD ON DATABASE, however it will improve the prformance of program, but LOAD ON DB will be incraesed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When ever u write a select statement to fetch the data from DB table, fisrt the control will go to DB table taking the FIELDS in WHERE condition , then it will check whetehr the Field (In where  condn) , exist in PRIMARY INDEX(PRIMERY KEY) of  the DB table  , IF not, then control moves to Secondary index (which u have cretaed ) and fetch the data, If field doesnt exist even in Secondary index , then it will go to remaing fields in the sequence maintaind in DB table.&lt;/P&gt;&lt;P&gt;Thats the reason in "WHere condn., it is suggested to USE INDEX fields".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as i know , when u craete secondary indeces more than 5, it wont affect any improve in performance , i.e Data base will treat the remaing Secondary indeces (all above 5) as normal key and not as Secondary index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rvert back if any issues,&lt;/P&gt;&lt;P&gt;Reward with points if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Oct 2007 07:09:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814263#M658020</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-04T07:09:03Z</dc:date>
    </item>
    <item>
      <title>Re: secondry indexes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814264#M658021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;secondary indexes can be used to speed up data retrieving&lt;/P&gt;&lt;P&gt;when u r using non primary key fields in where condition of a select statement&lt;/P&gt;&lt;P&gt; with out secondary index it wont fetch data&lt;/P&gt;&lt;P&gt;it fetches data only when there is corresponding secondary indexes&lt;/P&gt;&lt;P&gt;u can craete more than 15 indexes in atable&lt;/P&gt;&lt;P&gt;abap optimizer will  assign secondary indexes user has nothing to do with this&lt;/P&gt;&lt;P&gt;to avoid complications&lt;/P&gt;&lt;P&gt;it is better to resrict 5 indexes for achieving performances&lt;/P&gt;&lt;P&gt;reward for use ful points&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Nagesh.Paruchuri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Oct 2007 07:11:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814264#M658021</guid>
      <dc:creator>paruchuri_nagesh</dc:creator>
      <dc:date>2007-10-04T07:11:52Z</dc:date>
    </item>
    <item>
      <title>Re: secondry indexes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814265#M658022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hI &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;econdary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The database optimizer decides which index on the table should be used by the database to access data records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Oct 2007 07:12:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/secondry-indexes/m-p/2814265#M658022</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-04T07:12:07Z</dc:date>
    </item>
  </channel>
</rss>

