What is index

Hi All,
       I don't know it is a small Ques or Tuff one, Can any body please explain-
           difference between sy-index & sy-tabix. Every time iam confusing
           with them.
            Can anybody please explain with example.
regards,
ABAP Developer.

Hi Phaneendra,
There is a difference between the sy-index and sy-tabix.
Here if the itab1 consists 2 records and itab contains 10 records then sy-tabix
      loop at itab into wa_tab.
                  read table itab1 into wa_itab1 with key sy-tabix.
      endloop.
sy-tabix gives table index number mean table index = 2.
sy-index will give the counter in loop = 10.
sy-index give loop counter in a loop of (do enddo) (while endwhile)
sy-index does not work inside (loop endloop)
if we are looping into internal table the total number of loop pass is shown by sy-tabix.
if we are gonig for (do enddo) (while endwhile) number of loop pass is given by sy-index
Regards,
Kittu
Edited by: Kittu on Feb 6, 2009 12:35 PM

Similar Messages

What is index oragnized table

hi can you tell me
1.what is index oragnized table
2. fragmentation of table
3. what is cascading trigger mean

Hi,
For this points a good starting point are Oracle Manuals. For index organizated tables check this link [Overview of Index-Organized Tables|http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/schema.htm#sthref1044].
Cascading triggers should be avoided, see this link [Some Cautionary Notes about Triggers|http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/triggers.htm#sthref3187]
Regards,
Edited by: Walter Fernández on Jan 28, 2009 4:21 PM - Adding information about cascading triggers

What is indexing and why does it take 122 hours?

What is indexing and why has it slowed my computer and why does it take 122 hours?

Indexing allows Spotlght to know where everything is on your computer. It won't take as long as it says, the times it gives are always vastly inflated.

How to know what vertex index is picked on a Geometry?

I am trying to get the Texture coordinates which is picked on a geometry but I have got stuck to know what vertex index is picked.
My code:
pickCanvas.setShapeLocation((MouseEvent) event);
PickResult pickResult = pickCanvas.pickClosest();
Node node = pickResult.getObject();
GeometryArray geoArr = (GeometryArray)((Shape3D)node).getGeometry();
TexCoord2f texCoord = new TexCoord2f();
geoArr.getTextureCoordinate(0, ?, texCoord);Java doc said:
Class GeometryArray
public void getTextureCoordinate(int texCoordSet, int index, TexCoord3f texCoord)
Gets the texture coordinate associated with the vertex at the specified index in the specified texture coordinate set for this object.
Parameters:
texCoordSet - texture coordinate set in this geometry array
index - source vertex index in this geometry array
texCoord - the vector that will receive the texture coordinates
Thanks in advance.

I am trying to get the Texture coordinates which is picked on a geometry but I have got stuck to know what vertex index is picked.
My code:
pickCanvas.setShapeLocation((MouseEvent) event);
PickResult pickResult = pickCanvas.pickClosest();
Node node = pickResult.getObject();
GeometryArray geoArr = (GeometryArray)((Shape3D)node).getGeometry();
TexCoord2f texCoord = new TexCoord2f();
geoArr.getTextureCoordinate(0, ?, texCoord);Java doc said:
Class GeometryArray
public void getTextureCoordinate(int texCoordSet, int index, TexCoord3f texCoord)
Gets the texture coordinate associated with the vertex at the specified index in the specified texture coordinate set for this object.
Parameters:
texCoordSet - texture coordinate set in this geometry array
index - source vertex index in this geometry array
texCoord - the vector that will receive the texture coordinates
Thanks in advance.

What does indexing do?

Just what does indexing do? I clicked on a photo & asked the program to find a similar photo & the reply was that I would get better results if I indexed first. Now the crazy part I went to the PSE 10 manual & did a text search but the stupid manual is useless since it doesn't even contain the word 'indexing', the closest you get is a passing mention of 're-indexing'.

photodrawken wrote:
MichelBParis wrote:
What I have found is that this index is a file : itemdata.mk4 within the catalog folder.
If I'm not mistaken, the visual similarity searches also use data contained in the "WaldoData" directory, which has several files in it.
MichelBParis wrote:
What I still can't imagine is also how the resulting 'signature' can have a numerical order to be used in an index.
Ken
In PSE6 there is no Waldo subfolder, only in my PSE10.
photodrawken wrote:
MichelBParis wrote:
MichelBParis wrote:
What I still can't imagine is also how the resulting 'signature' can have a numerical order to be used in an index.
It wouldn't necessarily need a numerical order value. I don't have any idea how PSE does its Visual Similarity searches, either, but for purposes of discussion, consider this:
If one of the criteria used is "light coloured blob in the center of the image", then all PSE would have to do is store the image IDs of the images that fit that criteria. If a user uses an image with a light coloured object as the VS search item, PSE would use the index to quickly retrieve those image IDs and display images of, for example, portraits or a boat on the water, etc.
Quite a few years ago, IBM developed a "Query By Image Content" (QBIC) application which is stunning in its capabilities and accuracy. You can use QBIC at the State Hermitage Museum (St. Petersburg, Russia) Web site to search for images in its collection:
http://www.hermitagemuseum.org/fcgi-bin/db2www/qbicSearch.mac/qbic?sel Lang=English
Then I believe the word 'indexing' is slightly inadequate. It is rather a kind of multicriteria tagging.
I happen to use the visual similarity feature, but I don't use any of the autoanalyzer functions nor face recognition. I suppose the 'Waldo' subfolder was introduced for those automatic functions.

What are indexes

Hi Forum,
will any one please explain what are INDEXES.what are their USES, why do we create them and why do we drop them.any step by step procedure available to create them and drop them.at the same what are BW STATISTICS and what are their uses and how do we create them.
The only way i say thanx to help full answers is by assigning points.
Regds
Suhel
[email protected]

Hi Mohammad,
Creating and deleting indexes come with automatically when you design the process chains with your transaction data...
Both these (deleting and re-creating indexes) are used for the betterment of the BW system performance but in different areas..
for instance, its a usual practise to delete the indexes before loading a huge set of transaction data otherwise data loading will consume a huge amount of time to load each and every record based on the index that is already existing in the infocube... a record will go and sit inside the cube based on the indexes created for this cube... so its always advised to delete the indices before loading a huge set of data to improve the performance of data loading..
Now, the purpose of re-creating the indices after the data has been loaded is required in order to make data retrieval comparitively easier (during reporting).. When a query is being executed, data retrieval will always be faster when indices are created for the cube.. so that records are fetched based on the indices thats created for the cube instead searching the entire cube..
Hence, deleteing the indices before data loading enhances the performance of data loading and re-creating the indices after the data has been loaded improves the performance of data retrieval..
Hope it answers your question..
Regards
Manick

Just upgraded to Lion...What does indexing computer mean?

just upgraded to Lion...What does indexing computer mean?

It is finding and putting in order (indexing) all your files so that when you use Spotlight (the magnifying glass icon in the far upper right corner) it will find what you search for instantly, even as you are typing it. The first time it indexes it takes a long time, depending on how much is on your hard drive.

WHAT IS INDEXING IN DATABASE ?

WHAT IS INDEXING IN DATABASE ? HOW CAN WE USE IT ?
BEST REGARDS,
RYAN

Hi
Indexes can be defined in the ABAP Dictionary to speed up access to data in a table. These indexes are also created in the database.
Performance during table access
Indexes
Primary and secondary indexes
Structure of an index
Accessing tables using indexes
Primary and secondary indexes
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
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.
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.
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.
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
Database access using Buffer concept
Buffering allows you to access data quicker by letting you
access it from the application server instead of the database.
Advantages of buffering
Table buffering increases the performance when the records of the table are read.
As records of a buffered table are read directly from the local buffer of the application server on which the accessing transaction is running, time required to access data is greatly reduced. The access improves by a factor of 10 to 100 depending on the structure of the table and on the exact system configuration.
If the storage requirements in the buffer increase due to further data, the data that has not been accessed for the longest time is displaced. This displacement takes place asynchronously at certain times which are defined dynamically based on the buffer accesses. Data is only displaced if the free space in the buffer is less than a predefined value or the quality of the access is not satisfactory at this time.
Entering $TAB in the command field resets the table buffers on the corresponding application server. Only use this command if there are inconsistencies in the buffer. In large systems, it can take several hours to fill the buffers. The performance is considerably reduced during this time.
Concept of buffering?
The R/3 System manages and synchronizes the buffers on the individual application servers. If an application program accesses data of a table, the database interfaces determines whether this data lies in the buffer of the application server. If this is the case, the data is read directly from the buffer. If the data is not in the buffer of the application server, it is read from the database and loaded into the buffer. The buffer can therefore satisfy the next access to this data.
The buffering type determines which records of the table are loaded into the buffer of the application server when a record of the table is accessed. There are three different buffering types.
With full buffering, all the table records are loaded into the buffer when one record of the table is accessed.
With generic buffering, all the records whose left-justified part of the key is the same are loaded into the buffer when a table record is accessed.
With single-record buffering, only the record that was accessed is loaded into the buffer.
Buffering types
With full buffering, the table is either completely or not at all in the buffer. When a record of the table is accessed, all the records of the table are loaded into the buffer.
When you decide whether a table should be fully buffered, you must take the table size, the number of read accesses and the number of write accesses into consideration. The smaller the table is, the more frequently it is read and the less frequently it is written, the better it is to fully buffer the table.
Full buffering is also advisable for tables having frequent accesses to records that do not exist. Since all the records of the table reside in the buffer, it is already clear in the buffer whether or not a record exists.
The data records are stored in the buffer sorted by table key. When you access the data with SELECT, only fields up to the last specified key field can be used for the access. The left-justified part of the key should therefore be as large as possible for such accesses. For example, if the first key field is not defined, the entire table is scanned in the buffer. Under these circumstances, a direct access to the database could be more efficient if there is a suitable secondary index there.
With generic buffering, all the records whose generic key fields agree with this record are loaded into the buffer when one record of the table is accessed. The generic key is a left-justified part of the primary key of the table that must be defined when the buffering type is selected. The generic key should be selected so that the generic areas are not too small, which would result in too many generic areas. If there are only a few records for each generic area, full buffering is usually preferable for the table. If you choose too large a generic key, too much data will be invalidated if there are changes to table entries, which would have a negative effect on the performance.
A table should be generically buffered if only certain generic areas of the table are usually needed for processing.
Client-dependent, fully buffered tables are automatically generically buffered. The client field is the generic key. It is assumed that not all of the clients are being processed at the same time on one application server. Language-dependent tables are a further example of generic buffering. The generic key includes all the key fields up to and including the language field.
The generic areas are managed in the buffer as independent objects. The generic areas are managed analogously to fully buffered tables. You should therefore also read the information about full buffering.
Single-record buffering is recommended particularly for large tables in which only a few records are accessed repeatedly with SELECT SINGLE. All the accesses to the table that do not use SELECT SINGLE bypass the buffer and directly access the database.
If you access a record that was not yet buffered using SELECT SINGLE, there is a database access to load the record. If the table does not contain a record with the specified key, this record is recorded in the buffer as non-existent. This prevents a further database access if you make another access with the same key
You only need one database access to load a table with full buffering, but you need several database accesses with single-record buffering. Full buffering is therefore generally preferable for small tables that are frequently accessed.
Synchronizing local buffers
The table buffers reside locally on each application server in the system. However, this makes it necessary for the buffer administration to transfer all changes made to buffered objects to all the application servers of the system.
If a buffered table is modified, it is updated synchronously in the buffer of the application server from which the change was made. The buffers of the whole network, that is, the buffers of all the other application servers, are synchronized with an asynchronous procedure.
Entries are written in a central database table (DDLOG) after each table modification that could be buffered. Each application server reads these entries at fixed time intervals.
If entries are found that show a change to the data buffered by this server, this data is invalidated. If this data is accessed again, it is read directly from the database. In such an access, the table can then be loaded to the buffer again.
REWARD IF USEFULL

What the index means? in setCoordinate(int index...?

What the index means? in setCoordinate(int index...?
Although I looked at the API manual, but I still don't get it.
public void setCoordinate(int index,
double[] coordinate)
Sets the coordinate associated with the vertex at the specified index.
Parameters:
index - destination vertex index in this geometry array
coordinate - source array of 3 values containing the new coordinate

When you create geometry via a GeometryArray object the coords are stored in an array in which the order is important (eg a tri strip uses the last 2 coords and the current to draw a triangle, a tri fan uses the first, last and current to draw a triangle).
That method allows you to overwrite a coord at a specific point to change the geometry.

What are indexs?

Hi Experts,
Could any body tell me what are indexes .
What EXACTLY happens when we create the a indexs on a cube.?
Regards,
RG

Hi Friend,
Indices are used to locate needed records in a data-base table quickly.BW uses two types of indices, B-tree indices for regular database tables and bitmap indices for fact tables and aggregates tables.
These Bitmap indices cannot able to handle any inserts, updates, deletion. Bcoz of that we have to delete the indices before loading and have to rebuild it after loading.
But if u use the B-Tree indices there is no need for deletion of indices as B-tree can able to handle it very well.
B-tree indices: B-tree indices are used when dealing with huge volume of data. Line Item dimensions use B-tree indices.
Bitmap indices: for fact tables and aggregate tables: This is for regular database tables. Bitmap Indices can dramatically improve query performance when table columns contain few distinct values. Except LID other dimensions use bitmap indices
Thanks

What automated index strategy to use?

I have read about 3 methods to automatically update the context indexes: ctx_schedule, drjobdml and drbgdml.
We are currently using the ctxsrv.sh script but I heard that it's no longer supported. We are also using a nightly cronned rebuild script based on wwv_context.dropindex/createindex packages in the portal30 schema.
Is anyone using ctx_schedule, drjobdml or drbgdml? What are your experiences with it? Have you modified the script in any way? Etc...
Thanks!

I have read about 3 methods to automatically update the context indexes: ctx_schedule, drjobdml and drbgdml.
We are currently using the ctxsrv.sh script but I heard that it's no longer supported. We are also using a nightly cronned rebuild script based on wwv_context.dropindex/createindex packages in the portal30 schema.
Is anyone using ctx_schedule, drjobdml or drbgdml? What are your experiences with it? Have you modified the script in any way? Etc...
Thanks!

What is indexing?

When I tried to publish/share my video, indexing window popped up. It was just sitting there for 15 minutes and nothing happened.

dawnwong
For now I am assuming that your Premiere Elements 11 is on Windows 7 or 8 64 bit.
On what drive are your source media for the project?
Go to that drive, right click it, select Properties/General, and then check and uncheck the option at the bottom of the General area "Allow Indexing Service to Index this disk for fast file searching."
In troubleshooting here, complete details will expedite matters. Depending on your results with the above idea, lots of questions....
where are the source media for the project stored; is the drive formatted NTFS or FAT32; what is a description of your computer and its resources
what is on the Timeline targeted for your burn to DVD-VIDEO on DVD disc?
Let us start here and then decide what next.
Thanks.
ATR

What cause indexes to be corrupted?

I've an application that need to rebuild the indexes everyday or twice a day. I don't know why I have rebuild them so often. It's a big difference performance after the rebuild.
Thanks

The application is from Xeror (Docushare) and the back ends is Oracle. The application only has 9 indexes. Note, when I drop and recreate it performs much better and rebuild. That's too I don't understand too.
CREATE INDEX isRootElement_index ON
.DSObject_table(Object_isRootElement);
CREATE INDEX LookupUser_index ON
.DSObject_table(User_username, domain_name);
CREATE INDEX Stats_index ON .DSObject_table(handle_class)
CREATE INDEX Webdav_index ON
.DSObject_table(Object_webdav_title) ;
CREATE INDEX handle_id_index ON .DSObject_table( handle_id);
CREATE UNIQUE INDEX ACL_index_covered ON
.ACL_table(handle_index,
CREATE INDEX ACL_handle_id ON .ACL_table( handle_id,
Object_isDeleted ) ;
CREATE INDEX ACL_user_group_index on
.acl_table(user_group_index, user_group_class)
CREATE INDEX Link_index ON .Link_table(source_index,
source_class, linkType, destination_index, destination_class)
CREATE INDEX Link_breadcrumb_index ON
.Link_table(destination_index, destination_class)
CREATE INDEX Link_id_index ON .Link_table(source_id,
destination_id,linkType, source_isDeleted, destination_isDeleted)
CREATE INDEX Linktype_dest_index on .Link_table(linktype,
destination_id)
CREATE INDEX Pred_Index1 ON .DWE_Predecessors(Pred_Id)
CREATE INDEX Task_Index1 ON .DWE_Tasks(Workflow_Id)
CREATE INDEX Task_Index2 ON .DWE_Tasks(Parent)
CREATE INDEX Task_Index3 ON .DWE_Tasks(Template_Id)
CREATE INDEX Task_Index4 ON .DWE_Tasks(Resource_Id)
;

What r indexes?

hi all,
wat r primary index & secondary indexes? diff b/w two ?
regards
deepak

hi,
The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
We can create secondary index on non-primary key explicitly.
up to '9' secondary indexes we can create by using SE11.
Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that columns selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to, at most, five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
follow this link for creating seconadry index.
http://help.sap.com/saphelp_46c/helpdata/EN/cf/21eb47446011d189700000e8322d00/frameset.htm
for more information follow this link.
http://help.sap.com/saphelp_47x200/helpdata/en/cf/21eb2d446011d189700000e8322d00/frameset.htm
regards,
Ashok Reddy

What about Full-text indexing and search?

Great idea!
Has ORACLE NoSQL db this feature?
What about indexing/search using multiple languages simultaneously?
Thank you.

Hello Oleg,
Oracle NoSQL Database does not have these features. We may be considering them in a future release.
Charles Lamb

What is index

Similar Messages

Maybe you are looking for