We can also see if Lock Pages in Memory (LPiM) has been enabled, if priority boost is on or off, and if ‘max server memory (MB)’ has been set to a static value or not. What does the script output tell us here? Well, it shows us what kind of SQL Server instance we are running, at what build and edition, and how it has been configured when it comes to TempDB data files per core. *** I ran the script on a machine hosting a recent AX 2012 R3 build on SQL Server 2014 *** Microsoft Dynamics Learning Portal | AX | Course Catalog I also recommend that you take a look at the ‘SQL Optimization for Microsoft Dynamics AX 2012’ training courses ( 8046) if you have access to the Microsoft Dynamics Learning Portal. SQL Server topology recommendations for availability and performance Ĭonfigure SQL Server and storage settings For background information on this area, please see the official Microsoft Dynamics AX documentation, e.g.: Let’s start by looking at the SQL Server instance you are using to run your AX databases on. The scripts I provided look at the SQL Server instance and the AX databases deployed there. MSDN Blogs > Microsoft Dynamics AX Support > AX Performance – Checking key SQL Server configuration and database settings I will approach this from a Microsoft Dynamics AX perspective, first and foremost, though general SQL Server configuration guidance still applies to instances running an AX workload. ![]() ![]() There are of course different views on almost all SQL Server configuration settings, but the comments I will make are intended to be as in line as possible with other public documentation and Microsoft policies and best practices. This post aims to provide some feedback and suggestions on the information the scripts collect. In the previous post in this series, I provided some T-SQL scripts that can check key settings and highlight possible issues you need to address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |