web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Help with Cachelookup ...
Microsoft Dynamics AX (Archived)

Help with Cachelookup Property

(0) ShareShare
ReportReport
Posted on by Andre Savioli 635

hi.

I´m a SQL Server DBA working with Dynamics AX and i´m studying some concepts about the cachelookup property. i think can use SQL Server´s DMV sys.dm_db_index_usage_stats to help me  choosing the best option (Entire Table, found, foundandEmpty, notintts or None). Is it right?

 

I´ve read that´s not good use EntireTable in very large or heavily updated tables, beucase AX creates large tables  in disk and not place it in cache and this process has a high cost and heavily updated tables need to be flushed every time from AOS.

What about tables that have a lot of seeks, scans or lookups in sys.dm_db_index_usage_stats? Can i use these informations to help me in this choice?

 

Regards

*This post is locked for comments

I have the same question (0)
  • Andre Savioli Profile Picture
    Andre Savioli 635 on at

    very large i mean tables bigger than 128 kb.

  • Martin Dráb Profile Picture
    Martin Dráb 239,684 Most Valuable Professional on at

    Found, FoundAndEmpty and NotInTTS work in very similar way, so they are called together "Single Record Cache". To simplify the description (i.e. don't take this as the full truth), the record is added to/read from cache if it is found by table's cache key (often the primary key). The cache has limited size - 100 records on client and 2000 on AOS per table, I believe.

    So if you don't use the cache key to find the record, the cache is not used. Also, if you try to read a record after you cached more than 2000 other records, it's not in cache anymore and needs to be read from DB again. This is not what you can know just from the number of reads.

    I choose the cache type based on how the table is/will be used in the application, not on index statistics.

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.

Helpful resources

News and Announcements

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 21

#2
dekion Profile Picture

dekion 4

#2
Virginia99 Profile Picture

Virginia99 4

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans