Hi 

I have 2 errors when provisioning the database references.
The sync rules tab seems to be okay for both databases.

The errors I get are 3 minutes apart from each other.

First at hub (sync from hub to other):

Database provisioning failed with the exception "Invalid column name 'Id'.Inner exception: SqlException Error Code: -2146232060 - SqlError Number:207, Message: Invalid column name 'Id'. "    For more information, provide tracing ID 7c31cde5-4e10-4017-b0e9-d88ec3496f03 to customer support.

3 minutes later at the other:

Database provisioning failed with the exception "Cannot insert the value NULL into column 'provision_timestamp', table 'ServiceCruiserDB-shadowcopy.DataSync.provision_marker_dss'; column does not allow nulls. INSERT fails.The statement has been terminated.Inner exception: SqlException Error Code: -2146232060 - SqlError Number:515, Message: Cannot insert the value NULL into column 'provision_timestamp', table 'ServiceCruiserDB-shadowcopy.DataSync.provision_marker_dss'; column does not allow nulls. INSERT fails. SqlError Number:3621, Message: The statement has been terminated. "    For more information, provide tracing ID 8f439116-8819-44b2-94c6-2be5941bd5de to customer support.

Can you help please?

Hi,

Sorry for the late response.

Generally, when define the sync schema for a sync group, SQL Data Sync Service support 2 scenarios nowadays:

• Tables need to be sync only exist on one database. Then after you select this database -> refresh schema -> check the tables you want to put in sync -> click "save", those tables will be created on the other databases by SQL Data Sync Service, with the exactly same table schema.
• Tables need to be sync exist on all databases. In that case, after you save the schema, SQL Data Sync Service won't create/alter those table schemas for you. One thing you need to take care in this scenario is that you need to ensure those tables to be sync have the exactly same schema on all the databases in the sync group.

Back to your case, the first error: "Invalid column name 'Id'" indicated that you are trying to put a table with column "Id" in sync while your hub database doesn't have that column in the corresponding table. To resolve this error, please follow above 2nd scenario to ensure identical of the table schema on hub and member, or follow 1st scenario to drop the tables to be sync from hub and let SQL Data Sync create them for you.

For the second error "Cannot insert the value NULL into column 'provision_timestamp'", it seems to be caused by some redundant metadata of SQL Data Sync. To resolve, please remove this sync group and create it again.

In summary, to resolve the 2 issues on your sync group, please follow:

1. Remove this sync group
2. Follow above 2 supported scenarios to prepare tables to be sync on hub and member databases
3. Re-create this sync group

Please let me know if any more question.

Regards,
Bowen

Same errors again.

We'll try using the geo-replication functionality instead in the same datacenter.

Thanks