Cache

Table level cache has been performance improving feature. we can set both client and server side (AOS) level caches.

When cache at client and server side enabled. Then user query, first search will be done on client side cache, result not found then Ax tries to locate record at server side. In the case of record not found at server side, they will be fetch from table.

Client side cache is exclusive for every  client, while Server side cache can be access by any client.

we can set two types of Cache, Single record or set based Cache

In the case of single record based cache, we can set following properties in cache lookup

• NotInTTS,
• Found
• FoundAndEmpty
• CacheLookup is a method where some records will be loaded into memory at start-up of AX or when loading the table the first time.
  The setting Entire table will do the caching at start-up of AX. When it is a parameter table with one record or a group (setup) with a few records and this content is not supposed to change (once or twice a year) you can use the Entire table cache.
  When the number of records are enormous it will cause performance issues when starting AX. When you are changing the contents a lot (e.g. multiple times a day for records in that table) it could cause other sessions to keep working with the old cached data.