Overview

Customers may experience an issue related to maintaining consistent Tenant IDs after changing database names in their Evoq content environments for Production and QA. This could happen when the QA and Production environments are switched, resulting in the QA environment using the database name 'prod-db' and the Production environment using the database name 'qa-db'. The concern is that changing the database name results in a new Tenant ID, which is problematic as separate content needs to be maintained for each environment.

Solution

To maintain consistent Tenant IDs after changing database names in Evoq content environments for Production and QA, follow these steps:

1. Note down the current Tenant IDs for both environments before making any changes.
2. After changing the database name, create a support ticket and provide both the old and new Tenant IDs for migrating Liquid Content between them.
3. Be aware that if the QA environment starts using the database name from Production, it may inherit the same Tenant ID as Production.
4. To prevent this, verify and compare the GUIDs in the `HostSettings` table for both environments. If necessary, update the GUID for the QA environment to maintain distinct Tenant IDs.

Summary

By following the steps outlined above, you can maintain consistent Tenant IDs after changing database names in Evoq content environments for Production and QA. This ensures that each environment maintains its unique content when Support processes the migration.

FAQ

1. What happens if I don't note down the current Tenant IDs before making changes?
   If you don't note down the current Tenant IDs, you may face difficulties in migrating Liquid Content between the old and new Tenant IDs.
2. What if the QA environment starts using the database name from Production?
   If the QA environment starts using the database name from Production, it may inherit the same Tenant ID as Production. To prevent this, verify and compare the GUIDs in the `HostSettings` table for both environments.
3. How can I maintain distinct Tenant IDs?
   You can maintain distinct Tenant IDs by verifying and comparing the GUIDs in the `HostSettings` table for both environments. If necessary, update the GUID for the QA environment.