August 19, 2021 at 6:58 am
As mentioned in the link below,
For client-side applications, query notification users should not exceed ten concurrent users , in SQL Server 2005.
Will there be any performance degradation if we use around 200 concurrent users using query notification?
What is the maximum number of concurrent users allowed while using query notification in SQL Server 2008, SQL Server 2017 and above ?
August 19, 2021 at 9:50 am
As mentioned in the link below,
For client-side applications, query notification users should not exceed ten concurrent users , in SQL Server 2005.
Will there be any performance degradation if we use around 200 concurrent users using query notification?
What is the maximum number of concurrent users allowed while using query notification in SQL Server 2008, SQL Server 2017 and above ?
This post seems rather strange. The normal use case for query notification is to refresh cached data. You must be considering a system with tens of thousands of users if it needs 200 application servers. If this is the case a lot of other things will need to be considered; well beyond my experience.
Are you thinking of using query notification directly to a client application instead of the middle tier? Probably not a good idea.
Whatever you are planning I would suggest doing your own tests.
August 21, 2021 at 5:51 am
We have a single SQL server instance , to which 200 users(.net application) are connected and are waiting to receive notification from SQL server when a row has been updated via service broker. This is our scenario.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply