Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2021
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
One of the issues we have faced with all deployments is the difficulty of transferring the gold 'reference' configuration from the default tier-1 dev/test box across to the tier 2 UAT Sandbox, prior to go live. This has proved a very time consuming process.
Other than the process described here: https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/database/copy-database-from-sql-server-to-azure-sql , are there any recommendations on how to improve & speed up this process ?
Are there any plans to allow partners to submit a service request to copy a tier-1 across to a tier-2 environment ?
Thank you for this question, we do understand your pain. We have god news for you. There is a feature in preview right now that automates the flow. Here is how it works:
• Export the Golden Configuration database from your Tier-1 environment
• Upload that database to the Asset library in LCS
• Go to the sandbox (Tier-2 or higher) environment
• Go to Maintain button on the environment, there will be an option to Move database
We do not have a final release date yet, but it is actively being worked on.
I hope I answered your question. If so, can you please mark it as answered?
FastTrack Solutions Architect
To piggy back on this request - how about refresh from PROD to Tier 1 machines, allowing LCS refresh between T1 and T2 machines to streamline that?
Hi Nicholas, I agree that would also be very useful at times !
Claudia - is that a possibility as part of that feature ?
Ultimately, this is the idea. We will take it in stages, based on priority – first we want to land the direction from SQL Server to Azure SQL. Once that is completed, we will handle the other direction.
Business Applications communities