814
I did restore my production, which has stopped the restore procedure. i wentto azure and created new keyvault thing.
Now the problem is when i am trying to create another Data export profile I am getting some error, key vault is correct but not able to create it. is it because still old profile exist.
Do i need to delete old one to create new one, as old one has stopped working and it is on production
Any help.
Hey Ravi,
The old profile communication with your target DB on Azure went offline the moment it saw a copy/reset operation so we can safely delete the old profile.
We can delete the old tables and associated stored procedures by using this documented script.
docs.microsoft.com/.../replicate-data-microsoft-azure-sql-database
Post the above action, we can create a new profile and we should add entities one by one i.e once the complete sync gets acheived for an entity then another entity can be added so that the Azure SQL resource doesn't undergo immense compute resource.
Also, if you are sure that your Azure SQL DB subscription tier can handle the load, you can add multiple entities or even all entities in a single go. I have done it over trial orgs where I know the entity doesn't hold much data.
Hi Saurabh
I have created the new key vault.
should i delete old export profile hope it won't create any problem
After that from db i delete the table and stored procedure related to one table, and in new export profile I start this one table sync will that be okay and then when this one is successful, i repeat the step for all tables will that be okay? like delete 1 table and then go to export profile add table in it and synchronize it. Will that be good idea?
Hi Ravi,
You will have to anyways delete the old profile since Export Profiles must be deleted and then re-created whenever you perform any of the following actions on an environment.
Restore an environment.
Copy (either full or minimal) an environment.
Reset an environment.
Move an environment to a different country or region.
Additionally, you should also consider using a diffrenet prefix while creating the profile in case you would like to keep the old tables and stored procedures in the destination DB else you can delete them all and continue to use the old prefix and schema structure.
Ensure that the KeyVault resource on Azure has right orgID/TenantID tagged and has Data Export Service for Microsoft Dynamics 365 as an access policy principal associated with it.
Configuring the Azure Key Vault using Azure Resource Manager ::
Please mark my comments as answered if it helps
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (