Error encountered while deploying Azure Data Sync Template

Question

I am encountering the following errors while attempting to deploy an existing Azure Data Sync template to set up a new data sync.

Failed to perform data sync operation: '' is invalid schema master (Code: SyncOperation_GenericFailure)

Advisor 'DefragmentIndex' was not found for requested resource (Code: 45307)

Advisor 'DbParameterization' was not found for requested resource (Code: 45307)

The database ledger digest storage upload request does not exist or has no properties object. (Code: LedgerInvalidDigestStorageTargetUpdateRequest)

Could advice be provided on how to resolve these issues?

Answer 1

The errors you encountered while attempting to deploy an Azure Data Sync template seem to be related to the configuration or the environment setup. Let me walk through each error and provide some potential resolutions:

1. SyncOperation_GenericFailure: Invalid Schema Master

• This error indicates that the schema master is not properly defined or is invalid in the configuration. Resolution:
• Ensure that the schema of your Azure SQL database (the master database) is properly defined and matches the structure required for the Data Sync configuration.
  • Double-check the schema name or table names in your sync template configuration file to confirm they align with the current schema structure in your database.
  • If you’re setting up a new sync, you may need to update your sync group’s configuration to point to the correct master schema or update the sync metadata if there have been recent schema changes.

2. Advisor 'DefragmentIndex' and 'DbParameterization' Not Found (Code: 45307)

• The "Advisor" not found error usually happens when the specified advisor does not exist for the resource being targeted. Resolution:
• The database advisors DefragmentIndex and DbParameterization are part of SQL performance recommendations, which means these features or recommendations might not be supported or applicable for your current environment or configuration.
  • You can check the compatibility of the database tier (e.g., Standard, Premium) or version to confirm whether these advisors are applicable.
  • If these advisors are not required for your deployment, you may try removing or commenting them out from your configuration file to proceed with the deployment.
  • Alternatively, check with the Azure SQL advisor settings for your specific database if they need to be enabled or manually tuned.

3. LedgerInvalidDigestStorageTargetUpdateRequest (Code: LedgerInvalidDigestStorageTargetUpdateRequest)

• This error indicates an issue with the ledger digest storage configuration in your database. Resolution:
• If you are using the ledger feature, check your configuration to ensure that the "ledger digest" storage is correctly set up. Ledger digest storage is used to store tamper-evident logs for blockchain purposes.
  • Ensure that the storage account where the ledger digest is being uploaded has been correctly configured and that all necessary permissions are granted.
  • Verify that the ledger storage configuration includes a valid "properties" object with the required fields for the storage request.
  • If you’re not using ledger functionality, confirm that this feature isn’t mistakenly configured, and remove it from the template if unnecessary.

General Recommendations:

• Ensure that all dependencies are correctly set up in your environment.
  • If you're using Azure Resource Manager (ARM) templates or YAML deployment scripts, validate the configuration and ensure that each resource exists and is supported in your target environment.
  • Consider running az sql db sync commands manually through the Azure CLI to pinpoint configuration issues in more detail.

If the issue persists, reviewing the full template or providing additional logging details might help further pinpoint the exact cause of the deployment failure.