Reducing database fragmentation
View Patent ↗Techniques to reduce database fragmentation are disclosed. In various embodiments, an indication is received to store an attribute value for an entity that has a row or other entry in a first database table, wherein the first database table does not have a column for the attribute. It is determined that the value corresponds to a mapped value that is associated with not having an entry in a separate, second database table configured to store the attribute. Entries are made in the second database table only for values of the attribute other than the mapped value. Application level software code is configured to associate absence of a row in the second database table with the mapped value for the attribute.
1. A method of storing data, comprising:
storing, by one or more processors, a null value in a first database table in place of a first attribute value, wherein the first attribute value is mapped to the null value for storing in the first database table;
reducing, by one or more processors, fragmentation of the first database table, wherein reducing fragmentation of the first database table comprises:
forming, by one or more processors, a second database table and a third database table, wherein the second database table corresponds to the first database table without a column for an attribute corresponding to the first attribute value, and wherein the third database table is configured to store values for the attribute;
receiving, by one or more processors, an indication to store a second attribute value for an entry; and
determining that the second attribute value corresponds to a value that is mapped to the null value;
wherein entries are made in the third database table only for values of the attribute that are not mapped to the null value, and wherein application level software code is configured to associate absence of a row in the third database table with a mapped value for the attribute.
2. The method of claim 1 , wherein the second database table does not have the column for the attribute at least in part as a result of a transformation of the first database table.
3. The method of claim 2 , wherein the forming of the second database table comprises transforming the first database table by removing from the first database table a former column configured to store the attribute, and wherein the third database table is created and configured to store only those values in the former column that were not mapped to the null value.
4. The method of claim 1 , wherein the application level software code is configured to associate the null value for the attribute with the mapped value.
5. The method of claim 1 , wherein the first attribute value corresponds to a most common value for the attribute.
6. The method of claim 1 , further comprising receiving an indication to update a row in the third database table, determining that an updated value comprising the update is associated with a mapping to the null value, and deleting the row from the third database table based at least in part on the determination.
7. A system, comprising:
one or more processors configured to:
store a null value in a first database table in place of a first attribute value, wherein the first attribute value is mapped to the null value for storing in the first database table;
reduce fragmentation of the first database table, wherein reducing fragmentation of the first database table comprises:
forming, by one or more processors, a second database table and a third database table, wherein the second database table corresponds to the first database table without a column for an attribute corresponding to the first attribute value, and wherein the third database table is configured to store values for the attribute;
receive an indication to store a second attribute value for an entry; and
determine that the second attribute value corresponds to a value that is mapped to the null value;
wherein entries are made in the third database table only for values of the attribute that are not mapped to the null value, and wherein application level software code is configured to associate absence of a row in the third database table with a mapped value for the attribute.
8. The system of claim 7 , wherein the second database table does not have the column for the attribute at least in part as a result of a transformation of the first database table.
9. The system of claim 8 , wherein the forming of the second database table comprises transforming the first database table by removing from the first database table a former column configured to store the attribute, and wherein the third database table is created and configured to store only those values in the former column that were not mapped to the null value.
10. The system of claim 7 , wherein the application level software code is configured to associate the null value for the attribute with the mapped value.
11. The system of claim 7 , wherein the first attribute value corresponds to a most common value for the attribute.
12. The system of claim 7 , wherein the processor is further configured to receive an indication to update a row in the third database table, determine that an updated value comprising the update is associated with a mapping to the null value, and delete the row from the third database table based at least in part on the determination.
13. A computer program product to store data, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
storing, by one or more processors, a null value in a first database table in place of a first attribute value, wherein the first attribute value is mapped to the null value for storing in the first database table;
reducing, by one or more processors, fragmentation of the first database table, wherein reducing fragmentation of the first database table comprises:
forming, by one or more processors, a second database table and a third database table, wherein the second database table corresponds to the first database table without a column for an attribute corresponding to the first attribute value, and wherein the third database table is configured to store values for the attribute;
receiving, by one or more processors, an indication to store a second attribute value for an entry; and
determining that the second attribute value corresponds to a value that is mapped to the null value;
wherein entries are made in the third database table only for values of the attribute that are not mapped to the null value, and wherein application level software code is configured to associate absence of a row in the third database table with a mapped value for the attribute.
14. The computer program product of claim 13 , wherein the second database table does not have the column for the attribute at least in part as a result of a transformation of the first database table.
15. The computer program product of claim 14 , wherein the forming of the second database table comprises transforming the first database table by removing from the first database table a former column configured to store the attribute, creating the third database table is created and configured to store only those values in the former column that were not mapped to the null value.
16. The computer program product of claim 13 , wherein the first attribute value corresponds to a most common value for the attribute.
17. The computer program product of claim 13 , further comprising computer instructions for: receiving an indication to update a row in the third database table, determining that an updated value comprising the update is associated with a mapping to the null value, and deleting the row from the third database table based at least in part on the determination.
18. The method of claim 1 , wherein the first attribute value is equal to the second attribute value.