I have a desktop application which should be notified on any table change. So, I found only two solutions which fits well for my case: SqlDependency and SQLCLR. (I would like to know if there is better in .NET stack) I have built the both structure and made them work. I only able to compare the duration of a s̲i̲n̲gl̲e̲ response from SQL Server to the client.

SqlDependency

Duration: from 100ms to 4 secs

SQLCLR

Duration: from 10ms to 150ms

I would like this structure to be able to deal with high rate notifications*, I have read a few SO and blog posts (eg: here) and also am warned from a colleague that on mass requests SqlDependency may go wrong. Here, MS offers something which I didn't get that may be another solution to my problem.

*:Not all the time but for a season; 50-200 requests per sec on 1-2 servers.

On the basis of a high rate of notifications and in parallel with performance, which of these two should I go on with, or is there another option?