Today’s guest blogger is CRM MVP Joel Lindstrom, a Solutions Consultant for CustomerEffective.
For high availability Microsoft Dynamics CRM deployments, it is recommended that you have additional environments for test, Dev, and QA, so you can manage changes to your configuration without impacting users. This is also a good idea for disaster recovery, so if the production environment fails you can roll over to one of the other environments.
To have a valid test environment, you need to closely approximate your production Microsoft Dynamics CRM environment, with current configuration and data. So what is the process to "refresh" the data and configuration in your test environment to match the production environment?
Refresh a Microsoft Dynamics CRM test environment to match the production environment:
Drop the test MSCRM database in SQL Server Management Studio on the test SQL Server environment.
Thanks to Matt Parks and Ross Lotharius for their input. Ross notes that if you add users to the test environment that you imported, these users may get duplicated in the test configuration database and cause problems with these users logging in to the test environment. The recommendation is to either avoid adding users in the test environment (add them first to production before you import the organization into test) or restore both the MSCRM and configuration databases in step 4. Restoring the configuration database will work, as long as there are no other Microsoft Dynamics CRM organizations in the test environment.
Microsoft Dynamics CRM 4.0 Implementation Guide
Microsoft Knowledge Base article: How to move the Microsoft Dynamics CRM 4.0 deployment
Blog post: Deployment Manager: Import Organization vs. Edit Organization
Data migration overview
Blog post: Record Owner Information Migration using DMM
Due to a test marketing campaign incident, I now also overwrite email addresses for contacts, leads etc in test environment using a SQL script.
Is there any possibilities to do this with CRM 3.0? In 3.0 you dont have the "Import Organization" choice in Deployment Manager.
Does this process work for 2011 as well?