Golden Environment Prerequisites



Download 148.09 Kb.
Date27.10.2023
Size148.09 Kb.
#62432
Golden Configuration - Best practices

Golden Environment – Overview

  • Database movement operations are a suite of self-service actions that can be used as part of data application lifecycle management
  • Golden configuration" refers to a common practice among customers and partners in the Microsoft Dynamics ecosystem, where a developer environment is used as a configuration store.
  • Implementation projects can store finalized global and company-specific settings in a database that can later become a baseline for Conference Room Pilots, mock go-lives, and go-lives

Golden Environment – Prerequisites

  • A Dev VM with Database curated as Golden configuration i.e., set up and configuration data
  • At least one standard UAT environment
  • Dev VM must be on the same application version as the UAT environment
  • Platform version of the developer environment must be earlier than or the same as the platform version in the target UAT environment.
  • The only supported collation databases in the cloud is SQL_Latin1_General_CP1_CI_AS. The database collations in development environments are set to this value. Also make sure that any configuration environments that are published to sandboxes(UAT) have this collation.

Golden Environment – High level Steps(Refer URL for details)

  • Create a copy of source database
    • Use Tasks Back up
  • Prepare the database
  • Export the Database from SQL server
    • Download sqlpackage .NET Core for Windows from Get sqlpackage .NET Core for Windows.
  • Import the database
    • Upload the .bacpac file that was created in the previous step to the Database backup section in your LCS project's Asset Library. Then begin the import. The target UAT environment's databases will be overwritten by the golden configuration database.
  • Perform Master Data Migration ( UAT(Sandbox Step)
  • Copy the sandbox database to production (Cut over)
  • Reconfigure environment specific settings
  • Open environment to users
  • Limitations :

    • Encrypted and environment-specific values can't be imported into a new environment. After you've completed the import, you must reenter some data from your source environment in your target environment.
    • Reference : Golden configuration promotion - Finance & Operations | Dynamics 365 | Microsoft Learn


Download 148.09 Kb.

Share with your friends:




The database is protected by copyright ©ininet.org 2024
send message

    Main page