Schema different between hub and member database of data sync

Rhonda Cunningham 26 Reputation points
2022-06-21T20:12:37.957+00:00

When setting up data sync the schema in the member database is not identical to hub database. Specifically datetimeoffset scale is not the same and a unique, filtered index is missing the filter criteria, which causes sync to error.
Why are there changes in the schema on a direct copy. There is only 1 member at this time and the sync is 1 way from the hub.

How do I get the member database to have same schema as hub?

Azure SQL Database
0 comments No comments
{count} vote

Accepted answer
  1. Alberto Morillo 34,461 Reputation points MVP
    2022-06-22T10:17:41.47+00:00

    Create a dacpac (not a bacpac, but a dacpac) of the hub database using SQL Server Management Studio or other tool and store/upload the dacpac on an Azure Storage Account, after that create the member database from an import of the dacpac using Azure Portal.

    This will ensure the schemas are the same and it will make the initial sync faster.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.