brk325 from ax 4/2009 only new hardware bcp ~2500 target scripts can upgrade into multiple...
TRANSCRIPT
Upgrading to Dynamics AX 2012 R2
Andrew JewsburySenior Program ManagerMicrosoft Corporation
BRK325
Disclaimer© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. Other names and brands may be claimed as the property of others.
Microsoft Dynamics AX 2012 R2 is a pre-release product under development. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft. Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. All product release dates and features specified are preliminary based on current expectations, and are subject to change without notice. Microsoft may make changes to specifications and product descriptions at any time, without notice.
Sample code included in this presentation is made available AS IS. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS PRESENTATION. Microsoft products are not intended for use in medical, life saving, or life sustaining applications.
Session Focus
Key Takeaway #1
Understand new R2 upgrade
features
Key Takeaway #2
Requirements and Process for
In-place upgrade
Key Takeaway #3
Review Key Upgrade Best
Practices
Repeatable Process Continuity
New features
GLS countries
In-place Upgrade
Proscriptive Checklist
Partitioning
Challenges
Isolated data continuity
Concepts and Definitions
Source-to-Target upgrade modelParallel execution of data copy, data transformations & sync-on-the-fly to the target AX 2012
In-place upgrade systemA new upgrade approach to allow upgrade on existing source AX 2012 RTM system
PartitioningA logical barrier that isolates its business data from other partitions
Global Region Support
Global Region Support
APACChina, Japan, India
Eastern Europe
Latin America
Upgrade In Place
Key Differences
From AX 4/2009 onlyNew HardwareBCP~2500 Target ScriptsCan upgrade into multiple partitionsFast database synchronization
Source-to-TargetFrom AX 2012 onlyExisting HardwareNo BCP~50 Upgrade ScriptsOnly upgrade into a single partitionLonger database synchronization
Upgrade in-place
Sematic Live on R2 via Upgrade In Place
In-place Upgrade Processes
Createtest
system
Create development
system
Upgradecustomermodels
Testdata
upgrade
Upgradeproduction
system
AX 2012 or 2012 FPProduction system
ClientsAOS, Help, EP, etc.
AX database
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
SLN (Microsoft)
FPK (Microsoft)
GLS (Microsoft)
SYS (Microsoft)
Code layers
Busi
ness
dat
a
AX 2012 or 2012 FPTest system
ClientAOS, Help, EP, etc.
Busi
ness
dat
a
AX database
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
SLN (Microsoft)
FPK (Microsoft)
GLS (Microsoft)
SYS (Microsoft)
Code layers
Duplicate the production system
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
SLN (Microsoft)
FPK (Microsoft)
GLS (Microsoft)
SYS (Microsoft)
Code layers
AX 2012 or 2012 FPTest system
ClientAOS, Help, EP, etc.
Busi
ness
dat
a
AX database
AX 2012 R2
installer
AX 2012 R2 models from
Microsoft
ClientAOS, Help, EP, etc.
AX 2012 R2Test system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
Model store
LayerscontainingupgradedMicrosoft
models
Business data
Busi
ness
dat
a
AX database
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
Model store
AX 2012 R2
installer
ClientAOS, Help, EP, etc.
AX 2012 R2Test system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
Model store
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
SQL Servermodel store backup
Business data
Back up
ClientAOS, Help, EP, etc.
AX 2012 R2Development system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
Model store
ClientAOS, Help, EP, etc.
AX 2012 R2Test system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (customer)
CUS (customer)
VAR (customer)
ISV (customer)
Model store
Business dataBusiness data
Duplicate the test system
ClientAOS, Help, EP, etc.
AX 2012 R2Development system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
Model store
ISV
VAR
CUS
USR
Business data
1
2
Deleted models
VAR
CUS
USR
Models
`Models
Models
ClientAOS, Help, EP, etc.
AX 2012 R2Development system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
Exported ISV models
Models
ISV layer (2012 R2)
Export
1 2
Run code upgrade checklist
Business data
ClientAOS, Help, EP, etc.
AX 2012 R2Development system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
Model store
ISV (2012 R2)
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR
CUS
VAR
ISV
Model store
Model store backup
RestoreVAR
CUS
USR
Business data
ClientAOS, Help, EP, etc.
AX 2012 R2Development system
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR
CUS
VAR
ISV (upgraded)
Model store
Upgraded ISV model filesImport
Business data
Export newly upgraded models.
1
2
3
6
5
4
Starting with step 1, repeat for each
layer, working from lowest to
highest.
Run code upgrade checklist
Restore model store from backup.
Delete models in layers above
working layer.
Models
Working layerAssign the working
layer.
Import upgraded
models into their
layers.
AX 2012 R2Development system
ClientAOS, Help, EP, etc.
AX 2012 R2Test system
Model store
Restore
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (2012 R2)
CUS (2012 R2)
VAR (2012 R2)
ISV (2012 R2)
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (2012 R2)
CUS (2012 R2)
VAR (2012 R2)
ISV (2012 R2)
SQL Server model storebackup (upgraded)
Business data
ClientAOS, Help, EP, etc.
AX 2012 R2Test system
Model store
Run data upgrade checklist
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (2012 R2)
CUS (2012 R2)
VAR (2012 R2)
ISV (2012 R2)
Business data
AX 2012 or 2012 FPProduction system
ClientsAOS, Help, EP, etc.
Enter single-user mode
Busi
ness
dat
a
AX database
USR
CUS
VAR
ISV
SLN
FPK
GLS
SYS
AX 2012 or 2012 FPProduction system
ClientAOS, Help, EP, etc.
Replace Model Store and Split
DB
AX 2012 R2
installer
Model store
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (2012 R2)
CUS (2012 R2)
VAR (2012 R2)
ISV (2012 R2)
Business data
AX 2012 or 2012 FPProduction system
ClientAOS, Help, EP, etc.
Model store
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (2012 R2)
CUS (2012 R2)
VAR (2012 R2)
ISV (2012 R2)
Business data Run data upgrade checklist
AX 2012 or 2012 FPProduction system
ClientAOS, Help, EP, etc.AX 2012 R2 AOS, client, and other
components
AX 2012 R2
installer
Model store
SLN (2012 R2)
FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)
USR (2012 R2)
CUS (2012 R2)
VAR (2012 R2)
ISV (2012 R2)
Business data
In-place Upgrade Requirements
No 2012 RTM component can co-exist with R2 Must upgrade all components, there is no backward compatibility
(AOS/Client/Servers …)
Table per type mode is only for upgrade Controlled by a Stored Procedure installed during upgrade
Must upgrade to cumulative update 3 (CU3) before you move to R2
Recommend that production environment is running in CU3 before you upgrade to R2
Must keep IDs the same between 2012 RTM and R2Must upgrade your own custom schema and metadata
Key R2 Upgrade Features
Key R2 Upgrade Features
Proscriptive Checklist ChangesCode Upgrade ToolTable per type (TPT) v Table per hierarchy (TPH) modes
- “Register for Upgrade” puts you in TPT mode- Final Checklist item puts you in TPH mode
Reduced downtime windowKeeping Legacy ID Upgrading into Partitions
Upgrading into Partitions
C2
Virtual Company
P1
Upgrade
AX 4/2009
AX 2012 R2
P2
C3 C4
C2
Virtual Company
C3 C4
C1
C1
Partition Aware Data Upgrade Scripts
Script Type How it is executed
Number of script instances scheduled in the batch for
each script
StartScript, SharedScript, FinalScript Global, across all companies in all
partitions. 1
StandardScript Per company/per partition.
Number of companies (Notice that there is a DAT company in
every partition)
PartitionStartScript, PartitionScript, PartitionFinalScript
Per partition, cross companies in each
partition. Number of partitions
Upgrade Best Practices
Code Upgrade Best Practices (1/4)Investigate your features to see which ones are to carry
forward
Understand the Microsoft changes that impact your
upgrade
What new features replace your existing ones
What features are not used often (UI Elements)
Code Upgrade Best Practices (2/4)Complete the lowest layer upgrade first before moving to the next highest layerWork with ISVs and VARsUpgrade in dependency order
Fix your schema first, then code, then UI
Enum EDT Table Code UI
Code Upgrade Best Practices (3/4)Always click “Register for Upgrade” This installs a stored procedure to run AX in a TPT mode
Always be in a TPT database mode for code upgrade Always be in a TPH database mode in productionAlways follow the checklist stepsNever do preprocessing then import the AOD’s for code upgrade
Code Upgrade Best Practices (4/4)Never use xpo export/import for upgrades
If xpo absolutely required, make sure you keep IDs
Never delete Data Dictionary elementsUse SYSDeletedObjects
If absolutely required only delete metadata on targetSYSDeletedObjects62 is ONLY for In-place upgradeExisting 6.0/R1 license does not work in 6.2
Need the 6.2 license
Data Upgrade Best Practices (1/3)Complete Code UpgradeAlways click “Register for Upgrade” Installs a stored procedure to run AX in a TPT database mode
Always be in TPT database mode for data upgradeAlways be in a TPH database mode in productionResolve all production readiness errors Back up Database after each step!
Data Upgrade Best Practices (2/3)Always follow the checklistOnly perform Upgrade Readiness in production AFTER a successful complete end to end test run
Use the state transfer tool to reuse work
SQL Profiler and AX Performance Analyzer are useful for debugging performance slowdowns
Run through cleanup routines in some Periodic menus (e.g. SalesParam/PurchParm)
Database Upgrade Best Practices (3/3)Oracle Upgrade - Use Oracle to SQL migration toolDo not purge / leave behind companies
Upgrade all companies at once
Purge and Archive data via Intelligent Data Management Framework before upgradePlan at least two full test runs that are successful prior to running the live upgrade
You will have multiple test runs before the final oneCreate a list of post-upgrade validation tasks and plan how they will be tested
Related Sessions BRK313: Understanding Data Partitions in Microsoft Dynamics AX 2012 R2
Top tips from this sessions
Upgrade ContinuityContinuity provided from 6.0 to R2 and GLS to R2 scenarios
Partition UpgradeMove data into the correct partition to maintain business data isolation
Prescriptive UpgradesDetailed steps for a successful upgrade
PerformanceImproved performance to minimize your downtime
Best PracticesFollow best practices for a successful upgrade
Learn with Hands-on ExperienceFinancial Management:This ILL will lead you through the processes in Dynamics AX of the company consolidation and elimination business process. You will also have the opportunity to work with the new budgeting features available in Dynamics AX 2012 R2.
Managing Customer Returns:Get hands on experience on how to process a customer return in Dynamics AX 2012 R2. You will start with process of creating a Sales Quotation and end with sending receiving the Returned items back into inventory.
Retail:This ILL this help you gain better awareness about how to design the till layout that should be pushed down to the store terminals, you will also have the opportunity to complete other retail business processes.
Security:Interested in learning how to import users from Active Directory, assigning user roles, creating new roles, and also how to identify which roles need to be assigned in order to complete certain business functions?
Implementing Workflow:During this ILL you will learn how to setup a workflow and use this business function to create HR positions and complete other functions within the HR module.
Instructor Led Labs
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.