Difference between In Memory and Tempdb

                             

          In Memory                                                               Tempdb

1. Holds data temporarily in client or             1. Holds data temporarily in database

      server

2. These tables can't store in the database      2.These tables can store in the database.  

             .

3. Can't apply security.                                  3. Can apply security.   

Difference between ms dynamics 2009 and ms dynamics 2012?

1. security start from scratch
2. eliminate all EDT relations, and translate it to refrecID.
3. all journal posting classes have split-up in a validate, post and print class. so you have to split your customizations
4. Forms, go back to the defaults, first add your fields to existing field groups. otherwise create new field groups.
5. every code deserved his performance. generic solutions are slow, dedicated are fast.....
6. use the security profile tool, it is on information source.

History of MS Dynamics?

Microsoft Dynamics AX is an ERP solution in theMicrosoft Dynamics family.

 Microsoft Dynamics AX is a major player in the following types of businesses: manufacturing, distribution, services, retail and public sector organizations. As a single solution management tool, Microsoft Dynamics AX was designed and intended to handle complex business needs of larger enterprises.

Microsoft Dynamics AX was originally developed as a collaboration between IBM and Damgaard as IBM Axapta. Axapta was initially released in March, 1998 in the Danish and U.S. markets. IBM returned all rights in the product to Damgaard shortly after the release of Version 1.5. beforeDamgaard was merged with Navision Software A/S in 2000. The combined company, initially NavisionDamgaard, later Navision A/S, was acquired byMicrosoft in July 2002.^[4]

In September, 2011, Microsoft announced the release of new version AX 2012.^[5] Today, it is available and supported in 25 countries and 23 languages

Differences between RunBase & RunBaseBatch in ax

 RunBase class: The RunBase class is a framework for classes that need a dialog for user interaction and that need the dialog values to be saved per user. The RunBase application framework runs or batches an operation. An operation is a unit of work, such as the posting of a sales order or calculation of a master schedule.The RunBase framework uses the Dialog framework to prompt a user for data input. It uses the SysLastValue framework to persist usage data and the Operation Progress framework to show operation progress.

class RunBase extends Object implements SysSaveable, SysRunable

RunBaseBatch class: All jobs that must be able to run in a batch must inherit from this class. The RunBaseBatch framework extends the RunBase framework, and X++ classes that extend this framework can have their operations enlisted in the batch queue.

class RunBaseBatch extends RunBase implements Batchable
RunBaseReport class: The RunBaseReport class makes all reports batchable and creates a standard dialog box.

class RunBaseReport extends RunBaseBatch

This class is instantiated through the SysReportRun Class. It should be used by all reports. The purpose of the class is to:
 - Make all reports batchable
 - Create a standard dialog
 If you are creating more complex reports, it might be necessary to inherit from this class. If this is the case, you must create the following methods:
lastValueElementName(). Returns the report name.
description(). Static.
 main(). Static.