Performance
If your database is running slowly or the application data is not synchronizing correctly, you can perform some simple actions to clear things up.
Clearing the Cache
In this case, we mean the database cache (not the browser cache, although that might help some issues). Use this method if the metadata is not changing or updating.
| 1. | Within the Configuration Console, open the Cache Management workspace. The Cache Management page appears. |
| 2. | To clear all cached items, click Remove all cache items. This action removes all queried items from the memory cache on all application servers. |
| 3. | To clear only validation lists, click Reset cached validation lists only. This action removes all static-data validation lists from the memory cache on all application servers. This does not affect dynamic validation lists (such as employee). |
Indexing
You can index various fields within a business object. Designating a field as an Index field can help the search performance in some instances:
- Fields containing many (thousands) records that are frequently accessed by users can benefit from being indexed.
- Fields that are not well-used or have few records might be detrimental to performance if they are indexed.
- Too many indexed fields can slow down performance. The optimum number of fields is based on amount of access, number of users, and number of records, and is usually determined by trial and error.
|
These guidelines apply primarily to Cloud administrators. On-premise customers are responsible for tuning their own individual databases. |
A Cover indexAn index that contains all columns needed for a query. A search typically use indexes to speed up the resolution of which rows to retrieve, but then will go to the full table to retrieve the rows. contains all Included fields.
See Advanced for the procedure on creating an indexed field.
Indexing Group Objects
Group objects share fields with other objects and contain Derived objectA derived object is composed of fields from multiple objects and does not actually contain data.s. For example, Address is a group object.
For example: A sales area is determined by a BrokerID (with its own table), Company (with its own table) and StateID (with its own table). These three fields need to connect to a fourth table to pull proper information about sales area (i.e. Sales Area Number, Sales Reps, Sales Region, and Sales regional manager), and this fourth table also has BrokerID, Company and StateID fields. We need to connect three fields from three different tables to this fourth table. The fourth table is known as a Derived objectA derived object is composed of fields from multiple objects and does not actually contain data..
Derived objectA derived object is composed of fields from multiple objects and does not actually contain data.s list the base object indexed items. You can index the fields from this Derived objectA derived object is composed of fields from multiple objects and does not actually contain data., and at the same time, see which fields are indexed in the original objects.