Manage Connectivity studio parameters when copying database
In some cases, it can be required that you copy a database to another environment. For example, you have a test environment and a production environment. An issue occurs in the production environment. So, testing is required to find the cause of the issue. However, you do not want to mess up the production environment with testing data. You can copy the full production database to the test environment.
If you copy a database to another environment, the Connectivity studio parameters are overwritten with the parameter settings of the copied database. However, usually, you want to keep the original and unique parameter settings for an environment.
You have two options to make sure the Connectivity studio parameters are unique for the environment:
Before copying the database to an environment, export the Connectivity studio parameters from that environment. And after copying the database, import the parameters back to the environment.
After copying the database to an environment, delete the Connectivity studio parameters and set the parameters again. A disadvantage of this approach is that a new environment ID is generated. With a new environment ID, it is difficult to get back checked-out projects because these are checked out by another environment ID.
Prerequisites:
Before you copy a database:
From an environment, for example the production environment, make sure that all version-managed projects are checked in or get latest is done.
To an environment, for example the test environment, make sure that:
All version-managed projects are checked in.
The non-version-managed projects that you want to keep are exported. After copying the database, you can import these projects back into the environment.
If you have copied a database to the current environment and you want to manually reset the Connectivity studio parameters, first delete these parameters. As a result, all parameter settings are deleted, and a new environment ID is generated.
If the imported parameters are fine, you can also decide to only reset the Environment ID. As a result, only these fields are reset:
Environment ID: A new ID is generated for the environment.
Environment type: The environment type is reset to None.
Description: The description is reset to name of the current environment.
