title: mysql view and replication
body: <p>I'm asking for input on a tactical question: I am providing a master block of data (5-6 fairly large tables of frequently updated records) to multiple "client" sites that each have their own database serving other purposes. </p>
  
  <p>I was thinking that I could allow the "client" systems to access the master block of data in a couple ways:</p>
  
  <p>1) by simply replicating the data in the master tables into the client DB after each update process runs</p>
  
  <p>2) or possibly by creating the master tables as views in each client database.</p>
  
  <p>Is one tactic more efficient than another, or is there another process that I'm unaware of to serve this need? I realize storage is cheap, so the replication issue isn't probably that bad of a situation, but it's preferable not to have multiple copies to maintain.</p>
  
  <p>Thanks for your thoughts.</p>