Sites databases contain a large number of interfaces and property definitions related to optional features, such as FTR, concurrent engineering, and progress.
As a database grows, performance degrades. Therefore, when creating new class definitions, or reusing default class definitions, verify that all the interfaces are necessary in your customization. If you are using optional features, remove the interfaces associated with that functionality from your class definitions. Reducing the number of instantiated properties helps control the size of the database and assists with performance.
When modeling properties and interfaces, evaluate whether they can be optional and used only when there is data to add, rather than having interfaces with no properties and properties with no values.
Optional properties have IsRequired="False" on the exposes relationship to the interface. Properties that do not need values have IsRequired="False" on the scoped by relationship to the property type.