This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 19%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN6%3C/text%3E%3C/svg%3E)
Hi Team, I see that it is documented that we can have only one metadata database for a subscription/per region. When we have production and non production databases on the same region/Subscription with the same schema and object. Would it be a issue as the sync metadata database is the same for both production and non production environments.Can we ensure that production and non production environments dont cause discrepancies' in each others env
An Azure relational database service.
@Nitya V Same sync metadata DB should not affect sync itself. The sync Db is just used for storing sync configuration. There is no real data stored in sync Db. So you should not worry about the data integrity. The sync only happened between hub and member db. For your case, please use a dedicated db as sync Db instead of using sync db as hub db.
Regards
Geetha
If I understand it right we can have single metadata database shared across multiple combination of hub-member sync groups targeting different databases
@Nitya V Yes your understanding is right.
If this answers your question, please consider accepting the solution by hitting the Accept as Solution as it helps the community look for answers to similar questions.
Regards
Geetha
@Nitya V If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Regards Geetha
My recommendation is not to use SQL Data Sync in this scenario, any change in schema you want to test on DEV and the sync will be broken until you replicate those changes to the hub database. Maybe you may consider using Azure Data Factory to refresh the data on the Dev environment whenever you want with the Production data. You can also use Azure Data Factory to apply techniques of data masking (such as static data masking, dynamic data masking, substitution, shuffling, encryption, or hashing) to protect sensitive data coming from Production to the Dev database.
We aren't pulling data from prod to dev
Actual Scenario as an example on server1
Prod = dt 1 - Hub db
Prod = db2 - Member db
Prod = Metadata = metadatadt1 db
Dev= devdt 1 - Hub db
Dev= devdb2 - Member db
Dev= Metadata = metadatadt1 db So here the metadata database is same due to the limitation of one per subscription/region
SQL Data Sync is a tool use to sync data between databases, and you are telling me you are not pulling data from Production to Dev, so why then use SQL Data Sync? Please explain a bit more what you want to achieve between the databases in Prod and Dev/
We are using sync to separate the loads on a single PROD database into two separate databases in PROD for two different entry points. We are implementing the same on DEV environments as well as mentioned .The only shared thing is the metadata db used by the PROD sync group and Dev sync groups due to the limitation on 1 per subscription, There is no connection between dev and prod db.It is just the question on the using the same metadata db for PROD and DEV sync groups to ensure that it shouldn't affect the data integrity in the two environments
I have not tested that scenario. I am sorry. My suggestion is to update your initial question with the information you just provided to help receive the answer you are looking for.