Guideline needed for Multi-Remote-Server Management

Question

Hi all,
I'm busy with a project with multiple SQL servers, each with its own database.
The setup up is as follows:
6 SQL servers, where 1 is at the head office and the other 5 are remote branches.
I need to configure the following:
When Head office makes any changes to the Column: AveCost
in the dbo.STK_ProdPrice Table its needs to sync down to all the branches (when Head office does price increases on products). Now the update can run on a schedule (lets say 12am) so if the Table locks it would not cause any problems.
The SQL database structure for all SQL Servers are exactly the same (Exact same Tables, Exact same Column headings etc.) 
What would be the best solution for this configuration?

Answer 1

One option is Replication : Make your head office server as Publisher and keep all other 5 as subscriber ( transactional replication ). There
is no limit to to the number of subscribers that a publisher can support.
Another one is AlwaysON -- You can consider using Always 2012 but it will support only 4 replicas, may be you can think about 2014, this will support 8 Replicas, and this will keeps your data in sync..
sql 2012 -- https://www.simple-talk.com/sql/database-administration/sql-server-2012-alwayson/
SQL 2014 -- http://msdn.microsoft.com/en-us/library/gg509118.aspx
Raju Rasagounder Sr MSSQL DBA