Record Table Changes Notification From SQL Server To WPF Client

We are going to establish a communication between a WCF service and a WPF client using the wsDualHttpBinding that allows a Server application take the initiative to start an asynchronous communication with connected client, to notify them about an event.

I will not explain how to achieve this, because it is a well-known topic and it is also well explained here. I will focus on how to obtain communication between the database and a WCF server application.

Receive notification from database to Server application

Let's assume that we must implement a stock change service, reporting real time prices. Also, let’s assume that these prices are stored in a database table feed by an eternal provider, such as a broker from stock market exchange. As soon as this table is updated, we want to notify our WPF clients about the price change. We have seen that it is relatively easy to send notifications from a WCF service to connected WPF clients, but how we can achieve this from DB to WCF service?

Ideally, we want for our database to instantly notify our server application about record changes, allowing us to execute a periodical SELECT. But how to monitor SQL Server table changes? Some options are:

SQL Server Service Broker
.NET SqlNotificationRequest
.NET SqlDependency

All of these are work based on a notifications infrastructure. The first two options require us to have a good T-SQL and database knowledge to create database objects as service broker queue to monitor every change done on our records table, and notify us about any record table change. Although the last one does not require us to have this low-level knowledge, it presents a limitation: delivered notification does not report any information to us about which record has been changed, forcing us to perform a further SELECT to refresh the stock price.

Is it possible to receive record table change notifications containing modified, deleted or inserted records to avoid another SELECT to maintain updates to our cache?

Monitor table changes with SqlTableDependency

If we want get an alert about any table changes without paying attention to the underlying SQL Server infrastructure, then SqlTableDependency's record table change notifications will do that for us. Using notifications, an application can detect record changes saving us from having to continuously re-query the database to get new values.

SqlTableDependency record change audit provides the low-level implementation to receive database notifications creating SQL Server trigger, queue and service broker that immediately notifies us when any record table changes happen.

Push table change notifications using WCF Publish-Subscribe pattern

Let's assume that we have a table that is continuously updated with stock value from an external thread. We want our WPF application to be notified every time a stock price is updated without periodically checking the stocks table.

To achieve this, we need a service application that will take care of creating an SqlTableDependency object and for every change notification received, forward this new stock price to all interested WPF client applications.

For this, we are going to use a WCF service implementing the Publish-Subscribe pattern. This service will receive database notifications on any stock price change and in turn will notify subscribed WCF client applications.

Server application

For simplicity, we create a console application acting as WCF host. In this application, we create a C# model that will be filled by notification with the new table value.

public class Stock
{
public decimal Price { get; set; }
public string Symbol { get; set; }
public string Name { get; set; }
}

After that, we create the WCF service interfaces.

public interface IPriceChangeCallBack
{
[OperationContract]
void PriceChange(string code, string name, decimal price);
}
[ServiceContract(CallbackContract = typeof(IPriceChangeCallBack))]
public interface IPriceTicker
{
[OperationContract]
void Subscribe();
[OperationContract]
void Unsubscribe();
[OperationContract]
IList<Stock> GetAllStocks();
[OperationContract]
void PublishPriceChange(string item, string name, decimal price);
}

Now, we install SqlTableDependency nuget package in our server project.

PM> Install-Package SqlTableDependency

We now implement the WCF service. It creates an instance of SqlTableDependency pointing to the Stocks table: every record change on this table triggers a database notification that is cached from OnChanged event handler. Here, we simply push the new stock price to all connected clients.

[ServiceBehavior(
InstanceContextMode = InstanceContextMode.Single,
ConcurrencyMode = ConcurrencyMode.Single)]
public class PriceTicker : IPriceTicker, IDisposable
{
#region Instance variables
private readonly List<IPriceChangeCallBack> _callbackList =
new List<IPriceChangeCallBack>();
private readonly string _connectionString;
private readonly SqlTableDependency<Stock> _sqlTableDependency;
#endregion
#region Constructors
public PriceTicker()
{
_connectionString = ConfigurationManager
.ConnectionStrings["connectionString"]
.ConnectionString;
_sqlTableDependency = new SqlTableDependency<Stock>(
_connectionString,
"Stocks");
_sqlTableDependency.OnChanged += TableDependency_Changed;
_sqlTableDependency.OnError += (sender, args) =>
Console.WriteLine($"Error: {args.Message}");
_sqlTableDependency.Start();
Console.WriteLine(@"Waiting for receiving notifications...");
}
#endregion
#region SqlTableDependency
private void TableDependency_Changed(
object sender,
RecordChangedEventArgs<Stock> e)
{
Console.WriteLine(Environment.NewLine);
Console.WriteLine($"DML: {e.ChangeType}");
Console.WriteLine($"Code: {e.Entity.Code}");
Console.WriteLine($"Name: {e.Entity.Name}");
Console.WriteLine($"Price: {e.Entity.Price}");
this.PublishPriceChange(e.Entity.Code, e.Entity.Name, e.Entity.Price);
}
#endregion
#region Publish-Subscribe design pattern
public IList<Stock> GetAllStocks()
{
var stocks = new List<Stock>();
using (var sqlConnection = new SqlConnection(_connectionString))
{
sqlConnection.Open();
using (var sqlCommand = sqlConnection.CreateCommand())
{
sqlCommand.CommandText = "SELECT * FROM [Stocks]";
using (var sqlDataReader = sqlCommand.ExecuteReader())
{
while (sqlDataReader.Read())
{
var code = sqlDataReader
.GetString(sqlDataReader
.GetOrdinal("Code"));
var name = sqlDataReader
.GetString(sqlDataReader
.GetOrdinal("Name"));
var price = sqlDataReader
.GetDecimal(sqlDataReader
.GetOrdinal("Price"));
stocks.Add(new Stock {
Code = code,
Name = name,
Price = price });
}
}
}
}
return stocks;
}
public void Subscribe()
{
var registeredUser = OperationContext.
Current
.GetCallbackChannel<IPriceChangeCallBack>();
if (!_callbackList.Contains(registeredUser))
{
_callbackList.Add(registeredUser);
}
}
public void Unsubscribe()
{
var registeredUser = OperationContext
.Current
.GetCallbackChannel<IPriceChangeCallBack>();
if (_callbackList.Contains(registeredUser))
{
_callbackList.Remove(registeredUser);
}
}
public void PublishPriceChange(string code, string name, decimal price)
{
_callbackList.ForEach(delegate (IPriceChangeCallBack callback) {
callback.PriceChange(code, name, price);
});
}
#endregion
#region IDisposable
public void Dispose()
{
_sqlTableDependency.Stop();
}
#endregion
}

Let's set the endpoint binding.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<connectionStrings>
<add name="connectionString" connectionString="data source=.;initial catalog=TableDependencyDB;integrated security=False; User ID=Test_User;Password=Casadolcecasa1" providerName="System.Data.SqlClient"/>
</connectionStrings>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6"/>
</startup>
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior>
<serviceMetadata httpGetEnabled="true"/>
<serviceDebug includeExceptionDetailInFaults="true"/>
</behavior>
</serviceBehaviors>
</behaviors>
<services>
<service name="ConsoleApplicationServer.PriceChangeService.PriceTicker">
<endpoint address="get" binding="wsDualHttpBinding" contract="ConsoleApplicationServer.PriceChangeContracts.IPriceTicker">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
<host>
<baseAddresses>
<add baseAddress="http://localhost:8090/PriceTickerService/" />
</baseAddresses>
</host>
</service>
</services>
</system.serviceModel>
</configuration>

And to conclude, we code the hosting part.

class Program
{
static void Main(string[] args)
{
var host = new ServiceHost(typeof(PriceTicker));
host.Open();
Console.WriteLine($"Service started at {host.Description.Endpoints[0].Address}");
Console.WriteLine("Press key to stop the service.");
Console.ReadLine();
host.Close();
}
}

WPF Client application

As a first step, we need to create a WCF proxy to execute the price change subscription, and of course, to read the initial list of stocks. This operation can be done from Visual Studio - Run the server application and then, by adding a service reference typing the WCF URL endpoint.

We prepare the WCF client as follows.

<Window x:Class="DataGridSample.Window1"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Title="DataGrid Sample" Height="350" Width="776">
<Grid>
<DataGrid Height="302" Width="750" HorizontalAlignment="Left" Margin="10,10,0,0"
Name="McDataGrid" VerticalAlignment="Top" RowHeight="30" ColumnWidth="auto"
ColumnHeaderHeight="30" HeadersVisibility="Column" AlternatingRowBackground="Silver"
BorderBrush="Gray" BorderThickness="1" AutoGenerateColumns="False">
<DataGrid.Columns>
<DataGridTextColumn Header="Code" Binding="{Binding Code}" />
<DataGridTextColumn Header="Name" Binding="{Binding Name}" />
<DataGridTextColumn Header="Price" Binding="{Binding Price}" />
</DataGrid.Columns>
</DataGrid>
</Grid>
</Window>

Our client application executes an initial request to WCF, just to fill its Grid. After that, the application subscribes itself as a listener for price change notifications. In this way, every time a stock is updated, a notification containing fresh values is received.

public partial class Window1: Window, IPriceTickerCallback
{
private readonly IList<Stock> _stocks;
private readonly PriceTickerClient _proxy;
public Window1()
{
this.InitializeComponent();
var instanceContext = new InstanceContext(this);
_proxy = new PriceTickerClient(instanceContext);
_proxy.Subscribe();
_stocks = _proxy.GetAllStocks();
this.McDataGrid.ItemsSource = _stocks;
this.Closing += (sender, args) =>
{
try
{
_proxy?.Unsubscribe();
}
catch
{
// ignored
}
};
}
public void PriceChange(string code, string name, decimal price)
{
if (_stocks != null)
{
var customerIndex = _stocks.IndexOf(_stocks.FirstOrDefault(c => c.Code == code));
if (customerIndex >= 0)
{
_stocks[customerIndex] = new Stock {Code = code, Name = name, Price = price };
this.McDataGrid.Dispatcher.Invoke(DispatcherPriority.Background, new Action(() =>
{
this.McDataGrid.Items.Refresh();
}));
}
}
}
}

As the final result, instead of executing a request from client to the web application, and then the web application to the database; we are doing the reverse, i.e., sending a request from database to web application, and in turn from web application to clients.

5 Comments

Join the conversation! Your thoughts help the community grow.

Rajanikant Hawaldar7y ago
very good, nice article
Tridip Bhattacharjee9y ago
I like to thank you and all those people who write article in various web site. i like to share my experience about sql dependency. sql dependency is not very good and some time it can not detect changes and can not notify client too. one need admin rights in sql server to implement it. so it is not good if our database is hosted in shared environment. sql dependency is not push technology rather it is long polling. if anyone search google for sql dependency related issue then may see it has lots of down side. please do not mind because i have worse experience about it so said all the above. if possible we should avoid it. thanks
Tridip Bhattacharjee9y ago
It would be better if you provide your code sample in zip format so other people can run it. also mention what .net version you have used. thanks
Alaa Masalmeh9y ago
Good Explain... I may suggest to use Entity Framework instead o ADO.Net.
Amatya Agyey9y ago
Very clear and specific .. Keep it up Mr. Bianco