MFP: AX6 sneak preview - SQL AOD
Well MFP is giving us a sneak preview into AX 6.0 milestone. The AOD files are 'a changing'.
Check out the post here: MFP Blog Post: 'AX6 sneak preview - SQL AOD'
From the post:
"Today we built the first official build of Dynamics AX ever that does not run on AOD files. Starting today Dynamics AX's model database is stored in a Microsoft SQL Server database."
That's right, the Model Database will now be in a SQL Server Database.
More from the post:
"So far we have aimed at providing 1-to-1 parity with AOD files; but the potential of this is amazing - I hardly know where to start...
-Performance can be further improved as the subsystems querying the meta data store starts levarging the powers of SQL. For example; the ISAM database used for the AOD files (and still used by temp tables) doesn't support joins. Due to this many subsystems are overly chatty when reading meta data as they query row-by-row.
-Solving the element ID problem is now possible, as we can leverage the flexibilty and powers in SQL for modifying and extending the model schema.
-Capabilities... There are so many cool scenarios we can enable - but you'll have to wait for an sneak preview after the next milestone to learn more. But to get you thinking: What deployment capabilties did AOD files lack?"
My gears are already turning on how much better this will make the overall performance of the entire system work. True indexed model data, speed at the SQL level, this is for sure the right move.
I can't wait to hear more, thanks MFP for sharing and getting this out there.
"Visit the Dynamics AX Community Page today!"
Check out the post here: MFP Blog Post: 'AX6 sneak preview - SQL AOD'
From the post:
"Today we built the first official build of Dynamics AX ever that does not run on AOD files. Starting today Dynamics AX's model database is stored in a Microsoft SQL Server database."
That's right, the Model Database will now be in a SQL Server Database.
More from the post:
"So far we have aimed at providing 1-to-1 parity with AOD files; but the potential of this is amazing - I hardly know where to start...
-Performance can be further improved as the subsystems querying the meta data store starts levarging the powers of SQL. For example; the ISAM database used for the AOD files (and still used by temp tables) doesn't support joins. Due to this many subsystems are overly chatty when reading meta data as they query row-by-row.
-Solving the element ID problem is now possible, as we can leverage the flexibilty and powers in SQL for modifying and extending the model schema.
-Capabilities... There are so many cool scenarios we can enable - but you'll have to wait for an sneak preview after the next milestone to learn more. But to get you thinking: What deployment capabilties did AOD files lack?"
My gears are already turning on how much better this will make the overall performance of the entire system work. True indexed model data, speed at the SQL level, this is for sure the right move.
I can't wait to hear more, thanks MFP for sharing and getting this out there.
"Visit the Dynamics AX Community Page today!"
Labels: AOD, AX6.0, Blog, Dynamics AX 6.0, Future, Metadata, MFP, Model Database, SQL
posted by brandon | 5:09 PM
1 Comments:
If you are in the Minneapolis area you will want to attend the Microsoft Dynamics™ AX Executive Briefing.Bloomington, MN on May 20, 2009, to learn how you can benefit from Microsoft Dynamics AX! . A chance to hear Kirill Tatarinov (Corporate Vice President, Microsoft Business Solutions) share his worldwide vision about the future impact of business applications and Microsoft’s role in an ever-challenging economic environment. For more information on the event.
http://www.interdynbmi.com/news_events/MicrosoftDynamicsAXEvent.htm
Post a Comment
<< Home