索引六大规则（国外英文资料）.docVIP

索引六大规则（国外英文资料） Iron rule one: there is no such thing as a free lunch. There is a price to be paid for using indices. The benefits of indexing are obvious, but few people care about the cost of indexing. If a database administrator can have a full understanding of the cost of indexing, it wont be easy to index. In fact, the cost of indexing is quite large. It takes time and effort to create indexes and maintain indexes. In particular, when the database is designed, the database administrator needs to index the fields in the table, investigate, and coordinate. When the record in the table with the index is added, deleted, and modified, the database is retuned to the index. While the working database is automatically complete, the server resources are consumed. The more data the table has, the more resources it consumes. If the index is the actual object in the database, each index takes up a certain physical space. If you have more indexes, you will not only take up a lot of physical space, but also affect the performance of the entire database. You can see that database administrators still have to pay a lot of cost if they want to use indexes to improve performance. The database administrator is now thinking about how to achieve a balance between the two. Or, to find a critical point of return and investment. Iron law 2: dont build indexes for columns that are rarely involved in a query, or duplicate values. It is also a waste to build an index on this field if we do not query a field in the query. If we now have an employee information sheet, we may query employee information by employee number, employee name, or origin. However, we tend not to follow the id number. Although the id number is unique. At this point, even if you have indexes on this field, you cant improve the query speed. Instead, system maintenance time and system space are increased. Its just like moving a stone to your feet. In addition, there are a number of field repetition values for the emplo