You’re offline. This is a read only version of the page.
Hi,
We installed the 2.2 version of the monitoring tool last Friday to start collecting and reviewing our system for potential improvements. For the first few days everything went well, then yesterday (Tuesday) when all of a sudden our tempdbs started to grow out of control. The went from ~2.5GB per file (we have 8 tempdb files) to triple that filling the virtual disk in seconds. Thinking this was a fluke we expanded the disk size of the drive and kept monitoring only to have another rapid increase a few hours later. Environment:
1. Dynamics AX 2012R2 RTM / unpatched. Over 7 years worth of history is contained in the DB, we have a 200+ store retail chain
2. AIF used to integrate with magento 2.0 website
3. Scheduled Power BI jobs to load data to cloud
4. Standard client access via app
We have stopped the monitoring jobs from running to avoid another instance of this for now but would like to get them turned back on once we can figure out why the above might have happened. Has anyone else seen the tempdb grow so quickly when the monitoring jobs are running and if so how was it approached to prevent drives from filling up and causing errors across AX?
Thanks in advance,
Duane
Hi Duane,
Check these:
docs.microsoft.com/.../ms176029(v=sql.105)
www.sagecity.com/.../solving-the-question-what-causes-my-tempdb-to-grow
Regards
Share
Report
All responses (
Answers (
870
