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. Before you install a Microsoft Dynamics AX system, make sure that the system you are working with meets or exceeds the minimum network, hardware, and software requirements. 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. Since Axapta 3.0 SP3 with Kernel Update is supported on SQL 2005 (which is the level of our Axapta) you should be able to use SQL 2005 features, but it's not likely that SQL 2008 features will. ![]() || strStartsWith(sqlEdition, #SQLEDITION_DEVELOPER) Which sql version good for report development and for enterprise portal and role center. Need to move db from older sql version to latest sql version. and visual studio 2008 professional edition. & (strStartsWith(sqlEdition,#SQLEDITION_ENTERPRISE) We are using at present sql server 2005 standard edition with ax 2009 sp1. Public boolean isDataCompressionSupported() ![]() 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: 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |