If a table has many columns, and you query many different combinations of columns, it might be efficient to split the less-frequently used data into separate tables with a few columns each, and relate them back to the main table by duplicating the numeric ID column from the main table.
如果一个表有很多列,你查询列的许多不同的组合,这可能是有效较少用到的数据分割成独立的表有几列,和与他们回到主表表从主复制数字ID列。
That way, each small table can have a primary key for fast lookups of its data, and you can query just the set of columns that you need using a join operation.
这样，每个小表都可以有一个用于快速查找其数据的主键，并且可以使用连接操作只查询所需的列集。
Depending on how the data is distributed, the queries might perform less I/O and take up less cache memory because the relevant columns are packed together on disk. (To maximize performance, queries try to read as few data blocks as possible from disk; tables with only a few columns can fit more rows in each data block.)
根据数据的分布方式，查询可能执行更少的I/O，占用更少的缓存内存，因为相关列被打包在磁盘上。(为了最大化性能，查询尝试从磁盘读取尽可能少的数据块;只有几列的表可以在每个数据块中容纳更多的行。)
98
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
