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
This was a huge "NO-NO"! DBA's are taught to not shrink the SQL database because it can lead to very bad instability and data integrity problems,which is what you are having now. What you needed to do instead was run the maintenace wizard and focus on defragmenting indexes. Use Indexes to get around the performance bottlenecks that come with large databases.
We used to shrink databases back in the early 2000's when storage was very expensive, but there were always warnings and we worried when we did it. In today's time, this is not recommended because you will get all kinds of issues just as you are now.
You may be able to fix this issue through a painful process of replacing the forms or missing, unstable data but that will take a long time. Many people used to just restore a backup and then foward the new added information to the restored backup.
I'd say that you learned a good lesson about shrinking being bad, and that will save you a lot of work in the future.
Independent, Freelance Consultant and Dynamics Development Instructor
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13