Azure-docs: Issue with Syncing more than 30 Sync Agent

[waqar-anwar1990]

Issue with Syncing more than 30 Sync Agent

Okay our scenario needs us to sync more than 30 On-Premises DBs. Till 30 DBs it was all smooth. Now strangely, I am unable to sync the 31st and it keeps telling me that the Limit is reach. The exact error is here.

Failed to perform data sync operation: Quota 'SyncGroupMemberLimitPerServer' exceed, failed to create sync member.

Fair enough, after I encountered the error I now created a new Server with a different User and Created a New DB, but when I try to create a sync agent using the new user it gives me error when I try to make a connection when we are submitting the agent key.

Connection failed = Login failed for user 'newUser'..
Please check database credentials.
Other reasons of failure:
Firewall settings of local machine block connection to Sync Metadata Database.
Firewall settings of Sync Metadata Database block the connection.

To summarize, I have 30 syncs going on one server, when I do 31st it asks me the limit is reached, when I try to do sync on new server, it does not connect the agent on premises. Please advise me on what I need to do in order to get the process going further. Please help

I see a database called syncdatabase in my other/older server where I have already managed the 30 sync agents but I do not see that database here on the new server. I do not remember creating that DB on that server. Is it because of that? That's just my observation.

[Mike-Ubezzi-MSFT]

@waqar-anwar1990 Can you provide additional details as to which Azure services you are using, and any documentation you might be referencing that details the steps or procedures you might be following.

[waqar-anwar1990]

Thank you for your response Mike. Sorry I did not mention the links. I am using everything that is mentioned in the below documentation i.e. Azure SQL Databases, Sync Groups, and Sync Agents on-premises.

I have copied the details below.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e8439fa3-ed6f-94cd-107c-c2b00fa97d1a
• Version Independent ID: 0abf3b39-4fd0-a920-e5d2-8ae2bac650cd
• Content: Set up Azure SQL Data Sync (Preview)
• Content Source: articles/sql-database/sql-database-get-started-sql-data-sync.md
• Service: sql-database
• GitHub Login: @douglaslMS
• Microsoft Alias: douglasl

[Mike-Ubezzi-MSFT]

@waqar-anwar1990 I found the following information on a 3rd Party Site: Azure SQL Data Sync Limitations Pricing and Alternatives

System Requirements for Azure Data Sync

The Data Sync is a cloud feature, and there is not much to set up. However, for the On-premises SQL Server, here are the system requirements:

• A minimum of SQL Server 2005 SP2. However, it works best with SQL Server 2008 (R2 and later) as support for SQL Database was added to SQL Server Management Studio in SQL Server 2008 R2. Download a free trial from SQL Server Evaluations if you don’t have one.
• SQL Data Sync (Preview) only supports full editions of SQL Server and Azure SQL Database. Express versions of SQL Server are not supported.
• A Microsoft Azure account and subscription.
• A SQL Database subscription.
• You need at least one SQL Database deployed. If you need to host SQL Database instances in multiple data centers, you need a SQL Database implemented for each data center.
• Windows Server 2008 or later or Windows Vista or later versions of Windows OS.
• An x86 or x64 computer.
• The latest version of the Sync Agent.
• .NET Framework 4.5 or above

Now, that we have the system requirements clarified, let us look at some of the limitations.

• The maximum number of sync groups support is five (5)
• Maximum number of endpoints supported is thirty (30)
• Maximum On-premises endpoints supported is five (5)
• Maximum 12 filters per table being replicated. This is for performance reasons.

So, this confirms your findings.

[waqar-anwar1990]

@Mike-Ubezzi-MSFT so this means we cannot sync more than 30 endpoint/on-premises DBs? This is very strange.

Can you clarify if this is something that MS is working on, can I have an idea about its timeline when it will be available for more than 30 locations?

[Mike-Ubezzi-MSFT]

@waqar-anwar1990 This feature is 'In Preview' and I didn't find any Microsoft content related to limitations, requirements, etc., although I did find the information I posted previously. I am going to assign this to the content owner to see about getting feedback around what the requirements and limitations will be when it is no longer in preview status.

[douglaslMS]

This 30-endpoint limitation is mentioned in our published list of limitations: Requirements and limitations. This feature is in Public Preview, and General Availability is anticipated within the next few months. No significant changes to the feature are planned for GA.

[Mike-Ubezzi-MSFT]

@waqar-anwar1990 The Data Sync Agent functionality as you are currently working with, will be the same when it become Generally Available. We also have published a list of Requirements and Limitations.
Please communicate any additional questions that might have.
Regards,
Mike

[waqar-anwar1990]

@douglaslMS @Mike-Ubezzi-MSFT I would say the limitations are pretty ambiguous. I have already made 6 sync groups each for my Hub DB.

This makes 6 Hub DBs and 6 sync groups each having 5 on premises end points and 1 Hub DB. We were of the idea that there is a limit of 30 on one server where all these sync groups are created.

[douglaslMS]

@waqar-anwar1990 Our list of requirements and limitations doesn't mention any limitations per server, only per sync group. Which limitation in the list do we need to explain more cleary? Or, if you think there is a limitation that's missing from the list, please let us know. At first glance, "Maximum number of endpoints in a single sync group" appears unambiguous to me, but I have never been in your position of implementing SQL Data Sync on a large scale.

[douglaslMS]

in-progress

[waqar-anwar1990]

@douglaslMS I really appreciate this kind of reply coming from a senior guy, actually I solved my issue by creating a new SQL Server explicitly, previously I was creating the new server on the go while making the Database. Not sure why this happened but now I can sync more end points on my other server which is I wanted to do. Perhaps adding in the limits that 30 sync end points is the limit on server too.

Because I did not have 30 endpoints in one sync group but I had 5 sync end points in each of my 6 sync groups. I hope you understand my point here, also if you can close the issue after your response. Many thanks.

[douglaslMS]

@waqar-anwar1990 Thank you for the update. I'm pleased to hear that your implementation is now working as expected. I will review these limitations again with the SQL Data Sync program managers to see how we can make the limitations more clear and easy to understand.

[douglaslMS]

please-close