There isn't a lot of documentation on the internet about how to use the
SqlChangeMonitor with the new
MemoryCache class in .NET 4.0, so I thought I would add my example.
The first step is to prepare your database for
SqlChangeMonitor. This feature uses the SQL Server Service Broker to setup a notification event that fires to notify when data changes that would change the returned recordset of a query, so we have to enable the service broker on our database:
ALTER DATABASE database_name SET TRUSTWORTHY ON WITH ROLLBACK IMMEDIATE
ALTER DATABASE database_name SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE
ALTER AUTHORIZATION ON DATABASE::database_name TO sa
With that out of the way, we can continue on to setting up the cache in code…
public bool IsInMaintenanceMode()
if (MemoryCache.Default["MaintenanceMode"] == null)
CacheItemPolicy policy = new CacheItemPolicy();
string connStr = "MY CONNECTION STRING";
using (SqlConnection conn = new SqlConnection(connStr))
using (SqlCommand command = new SqlCommand(
"Select MaintenanceMode From dbo.MaintenanceMode", conn))
command.Notification = null;
SqlDependency dep = new SqlDependency();
inMaintenanceMode = (bool)command.ExecuteScalar();
SqlChangeMonitor monitor = new SqlChangeMonitor(dep);
MemoryCache.Default.Add("MaintenanceMode", inMaintenanceMode, policy);
inMaintenanceMode = (bool)MemoryCache.Default.Get("MaintenanceMode");
This code is a simple way to cache a value that specifies whether the application is currently in maintenance mode. The
dbo.Maintenance table contains a single row with a single bit column. This code will allow your application to continuously check to see if it should go into maintenance mode, without hammering your database.
When the value changes in the database, the application receives a notification that it should invalidate the cache. Then, in the next call to
null, causing it to re-register the notification. Just what we want.
- You must call
SqlDependency.Start first, otherwise it just doesn't work.
- Your SQL Command must follow the guidelines located here. There are lots of things to consider about how you build your query, so pay close attention to this document.
- After adding your command object to the
SqlDependency object, you must execute the command at least once, otherwise it will not register the notification.
- After executing the command once, you can dispose of your connection. Behind the scenes, .NET will keep a connection open to your SQL Server to listen for the notification.
I hope this helps some people out. I know I spent way too much time looking for documentation that just didn't exist.
- I have attached a sample project illustrating the use of the code above. It is a simple Console application that just shows how you might use this. Run the SQL script in the attached code to create a database, then run the application. Once it is running, change the value of "
MaintenanceMode" in the table. You will see when it is hitting the database, and when it is using the cache. I hope this provides a better example of usage.