Total Pageviews

Search This Blog

Thursday, May 19, 2011

Rank# 34 in the world, Rank#1 in Australia - Voting Results for 2011 Microsoft Dynamics Top 100 Influential People in World

The voting results for 2011 are out and this year my rank jumped to 34 from last year's 53 and Geographically, I have been ranked # 1 in Australia.

Geographically, Ranked #1 in Australia

Tuesday, May 17, 2011

Tip - How to avoid Overriding of SQL Indexes from AX when a Full Synchronization is done

There's this stored procedure written in SQL which retrieves historical order data and displays it on the Commerce Server Website. This SP uses almost 13 tables to retreive the data from (which includes custom and standard AX tables).

We added few indexes from AX to boost performance but in vain as when we run the Query Execution Plan, the Subtree cost of the index still shows more than 80%. SQL Server 2008 suggests new indexes which can be added via SQL to improve the performance of the query. I tried the indexes suggested by SQL and immediately the performance boost can be observed.

After some investigation, I found that the index added by SQL is different from index added via AX as AX doesn't have the capability to add the INCLUDE keyword when we create a new non-clustered index which SQL does as shown in the screenshot below

Here's something more about the include keyword from MSDN

Index with Included Columns
You can extend the functionality of nonclustered indexes by adding nonkey columns to the leaf level of the nonclustered index. By including nonkey columns, you can create nonclustered indexes that cover more queries. This is because the nonkey columns have the following benefits:
•    They can be data types not allowed as index key columns.
•    They are not considered by the Database Engine when calculating the number of index key columns or index key size.
An index with included nonkey columns can significantly improve query performance when all columns in the query are included in the index either as key or nonkey columns. Performance gains are achieved because the query optimizer can locate all the column values within the index; table or clustered index data is not accessed resulting in fewer disk I/O operations.


Whenever a synchronization is done, AX overwrites the indexes which we put through SQL


a. Created the index via AX as a table method

b. Modified the Application Class/dbsynchronize method so that after synchronization it invokes the table method to create index (mentioned above in Step a)

So, by doing this we have the SQL Indexes intact as we are recreating the index once AX finishes it's synchronization thereby avoiding the overwritten part

Tuesday, May 10, 2011

Resuming my blog after a break....

My Dear Blog Readers,

Sorry I was not on blogging for a while as took a short break from the routine hectic work life. I'm back now and resuming my work, have some interesting topics to cover so watch out this space.

Happy Dax'ing.