Announcements
No record found.
Attached is the screenshot of the tempdb size and growth.
Is this Perfect or I should increase the growth % .
Command used for attached output : use tempdb then exec sp_helpfile
Please advice.
regards
*This post is locked for comments
Hi Mazherullah,
I have split the thread where you posted this question as it was not related to the original question.
To be able to know the best size for your tempDB related to AX activities, you need to do some monitoring on size and growth. I cannot suggest if the current size and growth is correct for your environment as I don't know how it is used.
Note that growth in larger blocks is recommended. Standard SQL settings will auto growth in small portions which could lead to delays in responses.
Your settings are wrong. You need to have more TempDB data files, to avoid contention. Typically you have at least 4 TempDB files, and if you have an extremely large number of NUMA / CPU cores allocated to your SQL instance, then you may grow it further, so CPU threads could write to the files in a round-robin fashion.
Also growth should never be percentage-based! You would typically set it to grow by chunks between 100 MB - 1000 MB, both for data and log. We have set 8 files with a total size at 80 GB as our TempDB data file and 10 GB as log file size as pre-allocation.
Check the following blogs:
https://blogs.msdn.microsoft.com/axsupport/2014/09/05/ax-performance-troubleshooting-checklist-part-1a-introduction-and-sql-configuration/
https://blogs.msdn.microsoft.com/axsupport/2015/09/25/ax-performance-analyzing-key-sql-server-configuration-and-database-settings/
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.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
