Hello experts,
I am a SQL DBA supporting a Dynamics AX 2012 R3 CU10 environment. SQL is of version 2014 enterprise edition running off windows server 2012 R2 standard edition.
We currently are in deliberations and discussions to move from on premise to Azure.
My question surrounds areas on how to achieve increased IOPS and throughput for the AX Business DB on SQL Server Azure VM. Our current environment has SSDs (NVMe INTEL SSDPEDMD02) and another set of disks on - DELL PERC H730P Mini SCSI Disk Device. Both have excellent IOPS and throughput numbers.
- Does Microsoft Dynamics AX support (specifically for the AX Business DB) Table/Index partitioning on its objects?
- Does Microsoft Dynamics AX support changing table/index definitions to move them to different File Groups with its files spread over different disks, increase the disk IO paths and help achieve higher IOPS/throughput? My understanding was that tables/indexes in AX business database are considered as its kernel objects and changing them can lead to failure when one needs to perform a AX compilation or full synchronisation; is this correct? And if so does AX allow changing the table/indexes definitions in AX itself?
On Azure I am aware that we can implement Windows Storage Pools (on the SQL Server Azure VM) where you add as many physical disks, group them in virtual disks with Disk Striping and that can take you closer to your target IOPS/throughput and then carve out the desired volumes.
But is implementing table/index partitioning and/or configuring additional file groups and rearranging objects even possible (supported) by Dynamics AX. And is it worth the effort if Windows Storage Pool can assist with this.
If you can share any MS KBs or Whitepapers related to these questions it will be highly appreciated.
thank you for time.
Niraj Mehta
*This post is locked for comments
I have the same question (0)
