title: Using SQL Service broker vs Queues with web service
body: <p>We have a legacy system with central database (SQL Server) and small clients (KIOSK- with local DB (SQL Express)) which is writtent using WPF application. The data sync between client and central DB is done using C#, ADO.NET sql statements. This takes huge toll on the  performance. The number of clients currently we have are 400 and it will be increasing. Each client sends 100,000 records per day to the central database.</p>
  
  <p>We are planning to re-write this sync part using <strong>SQL Service Broker</strong></p>
  
  <p>One of the main issue, the schema between client and central DB is different. The tables were not normalized and the worst case is most of the columns were using nvarchar datatypes for storing datetime, intergers data.</p>
  
  <p>I am concerned about using Service Broker as most of the business logic would be written using Stored Procedure.</p>
  
  <p>I would like to get some ideas on whether using this technology would be the best or do we need to consider creating REST based service using Message Queue.</p>