It is safe to turn of PAGE compression in a Dev/Test/QA installation to save disk space, memory and potentially speed up your environment. In Production the general rule of thumb is to check ROW or PAGE compression improvements, make sure you have much more reads compared to write operations since there could be a write penalty for the latter one, and only do it for entries which have at least 100 pages of information. I would highly recommend the MSDN resources and articles below to determine for which tables and indexes is it safe or beneficial to turn on this feature. || strStartsWith(sqlEdition,#SQLEDITION_DATACENTER)))Īfter the adjustments, you will be able to open the SysSQLSetup form in AX to carry out the compression changes. In this episode with Anna Hoffman and Bob Ward, you will learn the benefits of connecting SQL Server to Azure Arc, including new improvements, new billing options for SQL Server and how you can onboard your SQL Server at scale with minimum effort. || strStartsWith(sqlEdition, #SQLEDITION_DEVELOPER) & (strStartsWith(sqlEdition,#SQLEDITION_ENTERPRISE) Public boolean isDataCompressionSupported() The Microsoft Dynamics AX 2009 download is a full install and required for new installations or upgrades from previous versions. Since Compression is a feature supported by version SQL Server 2008 (v10) and up, the code needs to be changed to cater for SQL 2012+ as per below: Dynamics AX 2009 - Microsoft Lifecycle Microsoft Learn Dynamics AX 2009 Dynamics AX 2009 follows the Fixed Lifecycle Policy. Unfortunately there is another case of hardcoded value from Microsoft, the SysSQLSetupHelper class is checking the version and the edition of SQL Server. In Microsoft Dynamics AX you are advised to do this via the client, otherwise your settings would be lost during the Data Synchronization. Data compression for tables and indexes are beneficial, especially for large tables within your SQL DB, where you are doing more read operations than writes.
0 Comments
Leave a Reply. |