Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
When ReleaseUpdateDB39_Vend.createDimHistory_PurchOrders_DSQL() runs, the transaction log for TEMPDB will grow until it consumes all available disk space.
We're working with 1TB drives. The AX database after conversion is roughly 321GB. The TEMPDB transaction log will attempt to grow to over 580GB, maxing out available disk space, during this one task. The task is not running with any other tasks.
Short of getting additional disk, is there a way around this? Is the InventReportDimHistory table esential to the operation of AX or can it be made a temporary table? (The first statement in the method asks if this table, the InventTrans or the VendPurchOrderTrans table is a temporary and, if so, returns without doing anything.)
You should set the logging mode of the database to Simple during upgrade.
Nope. Already in Simple recovery mode.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13