sqldependency

What are the limitations of SqlDependency

拥有回忆 提交于 2019-11-26 15:13:36
I am using a table as a message queue and "signing up" for up for updates by using a SqlDependency. Everywhere I read people are saying look out for the limitations of it but not specifically saying what they are. From what I've gathered you will have problems when the table has very high update frequency, fortunately I'm only looking at 10 - 20 values per minute maximum. What are the other limitations/impact on the SqlServer? The most complete list I can find ( from here ) is as follows: The projected columns in the SELECT statement must be explicitly stated, and table names must be qualified

Monitor data changes in SQL Azure

别来无恙 提交于 2019-11-26 14:47:44
问题 Is there a way to to get notifications when SQL Azure data changes or when new data is inserted? I would like to send notifications to an ASP.NET web application and push notifications to a Windows Phone. I know that the SqlDependency class and Query notifications are used to monitor SQL Server 2008 database data changes but SQL Azure doesn't support this yet. 回答1: Sorry but you don't have any options available other than rolling your own notification mechanism. One of the ways you could do

What are the limitations of SqlDependency

一笑奈何 提交于 2019-11-26 04:17:54
问题 I am using a table as a message queue and \"signing up\" for up for updates by using a SqlDependency. Everywhere I read people are saying look out for the limitations of it but not specifically saying what they are. From what I\'ve gathered you will have problems when the table has very high update frequency, fortunately I\'m only looking at 10 - 20 values per minute maximum. What are the other limitations/impact on the SqlServer? 回答1: The most complete list I can find (from here) is as

How do I clean SqlDependency from SQL Server memory?

折月煮酒 提交于 2019-11-26 00:34:34
问题 How do I clean up the SQL Server to get rid of expired SqlDependency objects? After I receive the event from the SqlDepedency object, I need to create a new one before I can get a new event. However, the memory use of the SQL Server process climbs until it runs out of the allowed memory (SQL Server Express). How do I get rid of old queries? Code: // Func: RegisterTableListener using (SqlConnection cn = new SqlConnection(Properties.Settings.Default.DatabseEventConnectionString)) { if (cmd ==