mysql视图和复制
我正在询问一个战术问题的意见：我正在向多个“客户端”站点提供一个主数据块（5-6 个相当大的频繁更新记录表），每个站点都有自己的数据库用于其他目的。
我想我可以允许“客户端”系统通过几种方式访问主数据块：
1）在每个更新过程运行后简单地将主表中的数据复制到客户端数据库
2）或者可能通过创建主表作为每个客户端数据库中的视图。
一种策略是否比另一种更有效，或者是否存在我不知道的另一种流程来满足这种需求？我意识到存储很便宜，因此复制问题可能并不是那么糟糕的情况，但最好不要维护多个副本。
谢谢你的想法。
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.
I was thinking that I could allow the "client" systems to access the master block of data in a couple ways:
1) by simply replicating the data in the master tables into the client DB after each update process runs
2) or possibly by creating the master tables as views in each client database.
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.
Thanks for your thoughts.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
允许任何客户端访问您的主数据是危险的。我会设置 MySQL 复制。您可以使用
--replicate-do-table=db_name.tbl_name将复制配置为复制特定表。正确设置复制后，您无需担心运行脚本来保持数据库处于正常状态。同步。
http://dev.mysql.com/doc/refman/5.0 /en/replication-howto.html
Allowing any client access to your master data is dangerous. I would setup MySQL replication. You can configure replication to replicate specific tables with the use of
--replicate-do-table=db_name.tbl_nameWith replication correctly setup, you won't need to worry about running scripts to keep your databases in sync.
http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html