Announcements
Hi Everyone..!!
Can any one tell me what is cache lookup and Entire table is not Best Practice but in which scenario we will take "Entire Table" .
*This post is locked for comments
HI Sai,
CacheLookup is a method where some records will be loaded into memory at startup of AX or when loading the table the first time.
The setting Entire table will do the caching at startup 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 enourmous 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.
CacheLookup
Determines how to cache the records retrieved during a lookup operation.
EntireTable
Creates a set-based cache on the server. The entire table is cached as soon as at least one record is selected from the table.
When you set a table's CacheLookup property to EntireTable, all the records in the table are placed in the cache after the first select. This type of caching follows the rules of single record caching. This means that the SELECT statement WHERE clause must include equality tests on all fields of the unique index that is defined in the table's PrimaryIndex property.
Avoid using EntireTable caches for large tables because once the cache size reaches 128 KB the cache is moved from memory to disk. A disk search is much slower than an in-memory search.
Please follow following link for more details
msdn.microsoft.com/.../bb278240.aspx
msdn.microsoft.com/.../bb314693.aspx
msdn.microsoft.com/.../bb314630.aspx
Please verify and update us with your findings
what are the other sub components like NotinTTS , found and FoundAndEmpty.
With Regards
Sai Rajesh
Please follow following link for details about NotinTTS , found and FoundAndEmpty
Please verify if this helps you.
And another link for table best practices: msdn.microsoft.com/.../aa632254.aspx
This also mentions some guidelines on the table caching.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
CP04-islander 10
Harisgillani 4
dserp 4
