StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Neither log shipping nor mirroring are replication solutions. They are high availability/disaster recovery solutions which allow you to have the <strong>same</strong> database in two (or more with log-sipping) locations. Only the source location can update the database.</p> <p>What you want is replication, see <a href="http://technet.microsoft.com/en-us/library/ms151819%28v=sql.105%29.aspx" rel="nofollow">Replicating Data to SQL Server Express</a>. Merge Replication will allow you to update data at the periphery (on the SQL Express instances). </p> <p>Note that all scenarios require <em>static and available</em> SQL Express instances. Replication will not work with if the SQL express instances are mobile (show up on the network with different names/IPs, think a laptop being moved around) or occasionally available (again, think a laptop that appears on and off the network as the user opens it in the corp WiFi or at home). For mobile/occasionally connected scenarios the right approach is <a href="http://msdn.microsoft.com/en-us/sync/" rel="nofollow">Sync Framework</a>.</p> <blockquote> <p>One thought was SSIS maybe from the central location pulling from the express instance, but again I don't know if this is possible.</p> </blockquote> <p>No, is not possible in practice, because of the impossibility of detecting changes ('what records need to be pulled?') and the lack of support for update conflict resolution. </p> <p>Another approach, which I did see it deployed with success, is to use <a href="http://technet.microsoft.com/en-us/library/bb522893.aspx" rel="nofollow">Service Broker</a> since is freely available in Express. But it only solves the problem of transport (delivery the changes), and does not address detecting changes (usually solved via either app specific logic or via triggers) and applying the changes (this is not hard to solve though). Update conflicts are hard to handle. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload