Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Hello everyone,I am having some difficulties with importing NAV DB from SQL Server to Azure SQL Server. I exported DB using Export Data-tier Application and trying to import it back using Import Data-tier Application. I googled the error but cannot find any solution. Does anyone familiar with this issue?
SQL Error:Could not import package.Warning SQL0: A project which specifies SQL Server 2016 as the target platform may experience compatibility issues with Microsoft Azure SQL Database v12.Error SQL72014: .Net SqlClient Data Provider: Msg 208, Level 16, State 1, Procedure deadlock_report_ring_buffer_view, Line 3 Invalid object name 'sys.dm_xe_session_targets'.Error SQL72045: Script execution error. The executed script:CREATE VIEW dbo.deadlock_report_ring_buffer_viewASSELECT target_data AS event_raw_dataFROM sys.dm_xe_session_targets AS xtINNER JOINsys.dm_xe_sessions AS xsON xs.address = xt.event_session_addressWHERE xs.name = N'..._deadlock_monitor'AND xt.target_name = N'ring_buffer';
Thank you for your help.Regards,Ekin
I have the exact same problem with a Business Central CU03 Cronus database. Haven't found a solution yet.
I think it is related to the newest CU's, I've tried CU 14 and 15, both Demo Databases having the same issue while importing to Azure SQL. I've tried CU 6 and I was able to import it without any issue. The problem is I cannot downgrade because I just upgraded from CU 6 to CU 14. Its been 2 weeks and a lot of new data is already in.
I've just removed SQL view called "deadlock_report_ring_buffer_view" from the database and successfully imported the DB, I've read some articles and apparently azure deals with deadlock by itself already. However, I don't know what the outcome will be.
Looks like a good workaround until Microsoft hopefully will get it fixed in the next CU. Thank you!
Business Applications communities