Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Dynamics 365 on prem Dev environment best practices

  • 1.  Dynamics 365 on prem Dev environment best practices

    Posted 11 days ago
    I am trying to setup a proper Dev environment for my Dynamics 365 on prem and understand some best practices.

    We are a pretty small organization (only about 35 users.) So right now I am using a single deployment of CRM and I have separate organization's within that for Dev and production which has worked good so far. I now want to test the new V9 and it looks like I can't just upgrade one organization to V9 to test, correct? I'm thinking I am going to have to setup a completely separate Dev environment on a separate machine? If I do that can I use my existing SQL Server (I have a separate SQL Server and Dynamics 365 Server) and just have a separate database or would it be best to setup a second SQL Server for Dev as well?

    Any feedback or advice would be appreciated.

    Thanks!

    ------------------------------
    Matthew Skowron
    HUB Industrial Supply
    ------------------------------


  • 2.  RE: Dynamics 365 on prem Dev environment best practices

    Posted 11 days ago
    Hi Matthew

    If you want to utilise your dev environment as a test platform before upgrading your prod to newer version of CRM, then you need Prod and Dev in separate server.
    If prod and dev is just a different org within same server, then you would not be able to upgrade one but not the other.

    After you separate dev and prod, you can go ahead to upgrade the dev first, fix any issue that comes up and package it into solution. Once test passed in dev, upgrade prod and then apply the solution that patches any issue with custom code you wrote and then do some quick testing.

    Once deployment in prod has successful and signednoff, you might want to refresh your dev environment using the copy of prod database to make sure they both in sync and dev is ready for next development cycle.
    Let me know if anything unclear. Happy to discuss further.




    ------------------------------
    Aylwin Wijaya

    ------------------------------



  • 3.  RE: Dynamics 365 on prem Dev environment best practices

    SILVER CONTRIBUTOR
    Posted 10 days ago
    • I now want to test the new V9 and it looks like I can't just upgrade one organization to V9 to test, correct? I'm thinking I am going to have to setup a completely separate Dev environment on a separate machine?
      • That is correct, you then transfer one of the organisation databases and import/upgrade it
    • If I do that can I use my existing SQL Server (I have a separate SQL Server and Dynamics 365 Server) and just have a separate database or would it be best to setup a second SQL Server for Dev as well?
      • You can use the same SQL Server (caveats) BUT it will have to be a separate SQL Instance.  Each CRM Deployment has a configuration database called MSCRM_Config, you can't rename it and there can only be one per SQL Instance
      • Caveat - need SQL 2016 or SQL v-brand new to support v9 so if you're on an older SQL version then you can't use that either

    Some other things to thing about:
    • Yes dev and UAT should be in separate deployments, not just separate Organisations but then there's only 35 of you and it's working well.  Just remember that if dev bring down the Async Service then they'll bring down test as well (plus some other Caveats)
    • If your Production environment is going to have IFD then you really should put that in Dev/UAT as well
    • There's been some worrying discussions on the Experience site about the build of v9 that was available for download - we may still be waiting for updated ISO
    • If the amount of Servers, time and effort to build all this on-premises for a 35 user system seems like a lot then, that may be partly by design as CE Online makes it all go away


    ------------------------------
    Andrew Wolfe
    Head of CRM Practice
    Technology Services Group
    United Kingdom
    ------------------------------



  • 4.  RE: Dynamics 365 on prem Dev environment best practices

    GOLD CONTRIBUTOR
    Posted 10 days ago

    Michael,

     

    You are correct – if you want to run two different versions of Dynamics 365 on-premise, you will need a separate deployment of CRM on a different server.  You can, however, share the same installation of SQL Server for both versions of Dynamics, as long as the version of SQL Server is compatible with both. 






  • 5.  RE: Dynamics 365 on prem Dev environment best practices

    GOLD CONTRIBUTOR
    Posted 10 days ago
    To clarify Michael's comment, "You can, however, share the same installation of SQL Server for both versions of Dynamics,".  But you must have a separate instance of SQL for each deployment.
    Andrew pointed this out in an earlier post, "You can use the same SQL Server (caveats) BUT it will have to be a separate SQL Instance. Each CRM Deployment has a configuration database called MSCRM_Config, you can't rename it and there can only be one per SQL Instance".



    ------------------------------
    Feridun Kadir
    Principal Consultant, MVP
    Expert CRM Services Ltd
    Stansted
    ------------------------------



  • 6.  RE: Dynamics 365 on prem Dev environment best practices

    Posted 9 days ago
    Edited by Wayne Wittman 9 days ago
    Mathew,

    Not sure if this is supported but you can share SQL instances.  You will need to rename the MSCRM_CONFIG database and update the configdb entry via regedit then cycle the CRM deployment.  You need to do this since the installation doesn't allow any control of the config database name.

    I found this workable since once the upgrade process is complete you will be removing the old instance anyway.

    As mentioned in other posts you do need a separate server for the CRM server itself.

    Wayne.

    ------------------------------
    Wayne Wittman
    CRM Administrator
    MiTek Industries Inc.
    Clifton NJ
    ------------------------------