Ref: http://myvirtualcloud.net/nutanix-scma-the-security-feature-that-could-save-your-organization/

In the scenario where SQL queries are running slower post-migration, creating multiple TempDB data files is a recognized best practice for optimizing SQL Server performance, especially when dealing with high transaction rates or complex queries. This approach helps in distributing the I/O load across multiple files and drives, reducing the contention and wait times associated with TempDB, which is a common bottleneck in SQL Server environments. Enabling autogrowth ensures that these files can dynamically grow as needed, which helps in handling unexpected increases in database activity without manual intervention.References:
Nutanix Best Practices for SQL Server, SQL Server performance tuning guidelines.

Ref: https://next.nutanix.com/installation-configuration-23/product-mixing-restrictions-37231

https://next.nutanix.com/move-application-migration-19/nutanix-xtract-validation-failed-user-must-belong-in-a-g

Addressing the customer's concern regarding the potential storage performance impact after a VM migration, it's important to note that Nutanix AHV includes intelligent scheduling mechanisms. AHV's built-in scheduler automatically works to restore data locality after VM migrations. Data locality refers to the placement of data close to the VM consuming it, which optimizes read and write operations by reducing latency. After migration, the scheduler actively moves data to ensure it is close to its consuming VM, thereby minimizing any adverse impacts on storage performance.
References:
* Nutanix AHV Administration Guide: Nutanix Documentation
* Nutanix Data Locality Explanation and Benefits: Nutanix Portal