Transcript Convergence_2008_AX20_Upgrading_AXx

AX20
Deepak Kumar
Program Manager
Microsoft Corporation
Michael F. Pontoppidan
Principal Developer
Microsoft Corporation
After this session you will...
● Understand the Microsoft Dynamics AX 4.0
and AX 2009 upgrade process
● Understand code and data upgrade flow
● Know tips and tricks on optimizing
an upgrade
● End-to-end upgrade overview
● Upgrade planning
● Code upgrade procedure
● Tips and tricks for code upgrade
● Microsoft Dynamics AX 4.0 SP3/Microsoft
Dynamics AX 2009 toolset
● Data upgrade procedure
● Data upgrade flow
● Performance enhancing tips for data upgrade
● Testimonial from a partner
● Q&A
Pre-upgrade
Plan your upgrade
Make backup
Create test environment
Code Upgrade:
Test
environment
Identify code conflict
Upgrade customizations
Data Upgrade:
Test
environment
Pre-data upgrade (cleanup, prepare data)
Data upgrade – walk through upgrade
checklist
Benchmark and Data verification
Production
Upgrade
Copy upgraded code
Walk through upgrade checklist
Verify
● Plan your upgrade
●
●
●
●
●
Process oriented documentation
Do business process analysis
Upgrade project plan
Upgrade performance goal
Upgrade verification plan
● Best practices
● Sure Step Upgrade methodology
● End-to-end upgrade overview
● Upgrade planning
● Code upgrade procedure
● Tips and tricks for code upgrade
● Microsoft Dynamics AX 4.0 SP3/Microsoft
Dynamics AX 2009 toolset
● Data upgrade procedure
● Data upgrade flow
● Performance enhancing tips for data upgrade
● Testimonial from a partner
● Q&A
Code upgrade
● Task
● Resolve conflicts caused by changes
in core functionality
● Timespan
● Weeks/months
(30% of implementation time)
● Goals
● Productive tools
● Reliable completion time
Layer technology
User: Site specific modifications for one customer site
Customer: Customer’s own modifications for the entire corporation
Partner: Business partner’s layer for customer specific functionality
Business: Vertical solutions made by business partners
Local: Country specific integrated certified solutions
Distribution: Servicing
Global solutions: Regional functionality
System: Standard application
Contents of the layer
● Application elements vary in size
● Forms and reports are big
● Tables, menus, queries are medium
● Fields, field groups, methods, etc., are small
Empty layers
● An empty layer is transparent
● Elements from lower layer(s) are used
Customizing
● Customizing existing elements will
● Copy of the existing element to your layer
● Hide existing elements
Upgrade conflicts
● During version upgrade, conflicts occur when
● You have customized an element, and
● Microsoft has changed the element
Version 4.0
Has Microsoft modified
the element ?
Yes
Have you modified
the element ?
Yes
No
No
Are our changes
identical ?
Yes
Ignore
Delete (obsolete)
No
Add to project
Version 4.0
Tips and tricks – for the implementation phase
● Avoid overlayering when possible
(adding new elements is not overlayering)
● Prefer overlayering of small elements
● Prefer overlayering of elements less
likely to change
● Implement unit tests
● If you transfer code in XPO files:
Always export and import with IDs
● IntelliMorph
● Use field groups
● Use extended data types
● X++
● Use class substitution
● For more information see
Smart Customizations on Channel9
Tips and tricks – for the upgrade phase
●
●
●
●
Upgrade one layer at a time
Use ”Show all Layers”
Use Create Upgrade Project
Take the easiest approach
● Reimplement your change, or
● Reimplement their change
Sneak preview of 4.0 SP3 / 2009
● Upgrade project
●
●
●
●
●
●
Detect conflicts
[New] Auto resolve simple conflicts
[New] Detect conflicts node by node
[New] Detect more conflicts types
[New] Visual indicators
[New] Progress tracking
● Compare tool
●
●
●
●
●
Show changes between two versions of an element
[New] Include information about the original (3-way compare)
[New] Better handling of renamed nodes
[New] Shortcut key + Moved to first level context menu
[New] Support actions in Forms
● [New] Estimation report
● [New] Element usage log
Sneak preview of 4.0 SP3 / 2009
Sneak preview of 4.0 SP3 / AX 2009
Sneak preview of 4.0 SP3 / 2009
Sneak preview of 4.0 SP3 / 2009
● Implement customizations with
upgradability in mind
● Upgrade one layer at a time
● Delete unused customizations
● Ensure consistent Element Ids
across environments
● Improved toolset in next Microsoft
Dynamics AX 4.0 SP and AX 2009
● End-to-end upgrade overview
● Upgrade planning
● Code upgrade procedure
● Tips and tricks for code upgrade
● Microsoft Dynamics AX 4.0 SP3/Microsoft
Dynamics AX 2009 toolset
● Data upgrade procedure
● Data upgrade flow
● Performance enhancing tips for data upgrade
● Testimonial from a partner
● Q&A
Data upgrade
● Task
● Upgrade company data for
Microsoft Dynamcis AX 4.0 and AX 2009
● Timespan
● Weeks/months
(Dependent upon data size,
data composition, resources)
● Goals
● Reliable completion time
● Production upgrade goal
● Major version and Service Pack go through the same
upgrade process
● Direct upgrade from 3.0SPx to AX 2009
● No direct upgrade path from 2.5 (SPx) to 4.0
2.5
3.0
SP1
SPx
SP
1
4.0
SPx
SP
1
SPx
AX
2009
Possible
Not Possible
Upgrade flow – highlevel
Pre-data upgrade steps
Install Microsoft Dynamics AX
4.0 / Ax 2009, don’t start AOS
Copy upgraded customization
code, start AOS
Walk through upgrade
checklist to complete upgrade
AX 3.0 upgrade only
● Left justify Microsoft Dynamics AX 3.0 data
● (Tool: PrivateProject_LeftJustified.xpo)
● 64bit conversion for RecId
● (Tool: PrivateProject_UpgradeColumnList.xpo)
● Move Microsoft Dynamics AX 3.0 data to
Microsoft Dynamics AX 4.0 DB / AX 2009 DB
● (Tool: DB prep tool)
Recommendation – common steps
● Source Database
● Delete duplicates – xpo available on PartnerSource
● Purge unneeded data – trace, transaction data
● Target Database
● Size your Microsoft Dynamics AX database correctly –
data, temp, log files
●
●
●
●
●
Transaction log – 50% of database size
Multiple log files – one file/logical CPU
Database logging minimal
Size DB files explicitly (though keep the autogrow)
Tune other DB settings – memory, etc.
Microsoft Dynamics AX 3.0 to AX 4.0 / AX 2009
Source
Axapta 3.0
PreUpgrade
Initialize
Target Microsoft
Dynamics AX
Leftjustify:
Cleanup data
Run in Parallel
after
PreUpgrade
Left Justify
(display
commands)
Copy
Upgraded
Code
64 bit RecID
Walk through
Upgrade
checklist
Source
Axapta 3.0
PreUpgrade
Initialize
Target Microsoft
Dynamics AX
Leftjustify:
Run in Parallel
after
PreUpgrade
Cleanup data
T1
T2
TN
Left Justify
(display
commands)
Copy
Upgraded
Code
64 bit RecID
Walk through
Upgrade
checklist
Source
Microsoft
Dynamics AX
4.0
In-place
upgrade
Target Microsoft
Dynamics AX
2009
Copy
Upgraded
Code
Cleanup data
Walk through
Upgrade
checklist
AX 2009
Upgrade Checklist
AX 4.0
Plan upgrade
Copy upgraded
code into right
application
directory
Walkthrough
upgrade checklist:
Code upgrade in
test environment
Install Microsft
Dynamics
AX4.0/AX2009
(select DB to
upgrade; don’t
start AOS)
Benchmark
and verify
Data upgrade in
test environment
Run DB prep tool
to move data
to AX4.0/AX2009
Production
upgrade
Ax 3.0 only
Purge/Cleanup
data/Delete
duplicates
Prepare Data –
(Leftjustify,
64bit ReciD)
Documentation/
Training
SQL Server
Oracle
Common
Set Recovery Mode = Simple
Size TEMPDB to a large Value (20GB) on good disk
Size LOG High – Upgrades are Log Intensive
SET AWE Memory, if DB Server has Large Memory
SET Max Degree of Parallelism to Zero
SET Max Memory to at least 80% of physical memory
Set Tablespace Logging off
Make sure Tablespaces do not grow during upgrade
Make sure SGA is sized to use 80% of physical memory
Track performance using Snapshot reports
Statistics Updates where applicable
Monitor test runs for better handle on index set
Maximize index creation parallelism based on I/o Capacity
● When you have a large number of companies
● SQL Plans are not effective if the first company
does not have large data
● Mitigation: Use SQL 2005 Plan Guides to force
recompiles
● We have cases where data upgrade duration go for
38+ hours without recompile to about 2 hours with
recompile http://msdn2.microsoft.com/en us/library/ms190417.aspx
● Turn AX specific table logging off, unless
absolutely necessary
● Run Synchronization in parallel for AX 2009
● Upgrade is dependent on data composition
● Test with a copy of production data
● Purge uneeded data by running cleanup scripts
● Upgrade performance is dependent on
database configuration
● Tune your database for maximum performance
– memory settings, data/log files
● Turn database logging to minimal
● Benchmark test results
● If having performance issues
● Find biggest culprit
● Trace the problem – database tracing
provides good clue
● Make sure database statistics are current
● Monitor memory, IO, database file size
● Improve parallelization
● AX 4.0 – running multiple AX clients
● AX 2009 – configurable through batch threads
● Focused on solving major upgrade pain points
●
●
Reduce data upgrade cycle
Improve usability of upgrade tasks
● New features:
●
●
●
●
●
●
●
●
●
Skip one major version
Use of server bound batch framework for upgrade
Focus on parallelization – framework, execution, synchronization
Run all failed script with a single click
Inform user about database logging level and recommendation
Improved upgrade checklist to align with upgrade process
Upgrade cockpit with new feature for execution, control, status
Automated EP and AIF upgrade
Many other optimization and features
● End-to-end upgrade overview
● Upgrade planning
● Code upgrade procedure
● Tips and tricks for code upgrade
● Microsoft Dynamics AX 4.0 SP3/Microsoft
Dynamics AX 2009 toolset
● Data upgrade procedure
● Data upgrade flow
● Performance enhancing tips for data upgrade
● Testimonial from a partner
● Q&A
Paul Langowski
Chief Architect
Tectura
Axapta 2.5 to AX 4.0
●
●
●
●
900 total users / 70 locations
160GB database migration (< 20 hours)
900+ Modifications in 2.5
Cutover in a single weekend
Axapta 3.0 to AX 2009
● 100 users
● 30GB database (< 3 hours)
● Scheduled for Pre-launch go-live on AX 2009
● Microsoft Dynamics AX 4.0
Implementation Guide
● Upgrade white paper
● PartnerSource; CustomerSource
● Elements changed between versions
of Microsoft Dynamics AX
● PartnerSource; CustomerSource
● Upgrade known issues
● PartnerSource; CustomerSource
● How to write Upgrade scripts – white paper
● End-to-end upgrade overview
● Upgrade planning
● Code upgrade procedure
● Tips and tricks for code upgrade
● Microsoft Dynamics AX 4.0 SP3/Microsoft
Dynamics AX 2009 toolset
● Data upgrade procedure
● Data upgrade flow
● Performance enhancing tips for data upgrade
● Testimonial from a partner
● Q&A
● W311E – Room 8
● 11:00 am – 12:00 pm
● For more information and additional
questions, comments:
[email protected]
Your feedback is important!
● Two ways to access online evaluation forms
● CommNet and evaluation stations located throughout
the Orange County Convention Center
● From any wired or wireless connection to
http://www.msconvergence.com
Be eligible to win great daily prizes and the
grand prize – a $5,000 Travel Voucher!
For more information please refer to your Conference Guide
Note: You must complete an evaluation form in order to be eligible to receive a Convergence 2008 Conference DVD set
We want to hear from you!
What is Microsoft doing well?
What can Microsoft improve?
● Where? Community & Learning
Center
● When? During Convergence Hours
Change happens when you
SPEAK YOUR MIND
● What is it?
● The Microsoft Dynamics Customer Reference Program showcases real-life
results of customers successfully using Microsoft Dynamics solutions
● Why is it important?
● Opportunity for Microsoft to promote your success worldwide
and gain rewards
● Provides exposure to you and your company through
● Case Studies, Press Releases, Industry Analyst Interviews,
Webcasts Videos, User Group Networking, Free Memberships,
and Customer-to-Customer Meetings & More!
● Where can I find more information?
●
●
●
●
●
Microsoft Product Pavilion Booth # 19 or the Community & Learning Center
How do I join?
Microsoft Product Pavilion Booth # 19 or Community & Learning Center
Microsoft Customer Source
Send email to [email protected]
© 2008 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.
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.