Data Sync - Adding On Prem DB is "Add Failed"

Murugesh Perumal 0 Reputation points
2026-07-31T03:52:19.2166667+00:00

Adding On Prem DB is "Add Failed"

Failed to perform data sync operation: Cannot create sync member 'XXX_1' because the maximum number of on-premise database as sync member can be created under a sync group is 5 for Basic sync group, But i have only 2. Before it was 4 and those are deleted. Also when i check the number of members ,

PS /home/aaa> $Members = Get-AzSqlSyncMember `

-ResourceGroupName $ResourceGroup `
-ServerName $ServerName `
-DatabaseName $HubDatabase `
-SyncGroupName $SyncGroup

PS /home/murugesh>

PS /home/murugesh> $Members | Format-Table SyncMemberName, MemberDatabaseType, SyncDirection, SyncState, SqlServerDatabaseId -AutoSize

SyncMemberName MemberDatabaseType SyncDirection SyncState SqlServerDatabaseId


aaa_1 SqlServerDatabase OneWayMemberToHub SyncSucceeded aa91-eca9-4b58-ac32-2da7f3

Azure SQL Database

1 answer

Sort by: Most helpful
  1. Smaran Thoomu 495 Reputation points Microsoft External Staff Moderator
    2026-08-18T12:47:17.94+00:00

    Hi @Murugesh Perumal

    First, please accept my sincere apologies for the delay in responding and thank you for your patience.

    Based on the information shared, it appears that the issue is not related to the current number of visible sync members in the Sync Group. Although only one on-premises sync member is currently listed, the service is still reporting that the maximum number of on-premises databases has been reached for a Basic Sync Group.

    Since the previous on-premises server crashed and several sync members were removed and recreated, it is possible that stale synchronization metadata remains associated with the Sync Group configuration.

    As a troubleshooting step, please ensure that:

    • All old databases are unregistered from the Data Sync Agent.
    • Unused sync members are removed from the Sync Group.
    • The Data Sync Agent service has been restarted after the cleanup.
    • A new Sync Group is created and tested with the on-premises databases.

    If the issue continues even with a newly created Sync Group, further investigation please let us know to review the Sync Group configuration and associated metadata.

    Please let us know the outcome after testing with a new Sync Group, and we'll be happy to assist further.

    Was this answer helpful?

    0 comments No comments

Your answer

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