Q – looking for examples/tutorial of 5NF/or 6NF, pref for custom user fields, details below
While doing some research on adding custom user fields like in outlook and the pro/cons of various approaches, came across using the 6NF at
How to store custom user fields in database
and
What are the [dis]advantages of using a key/value table over nullable columns or separate tables?
quite frankly the theory went over my head so looking for any examples/tutorial of 6NF, pref for custom user fields or any insight into how its done in outlook
The answer that mentions 6NF in relation to custom fields is a red herring. There is no possible way of modelling 6NF in SharePoint lists or outlook metadata.
The SharePoint developer/administrator does not have much control over the resulting queries (list views) that the interface provides, specifically there is no way to provide more than one field from Lookup columns. This limits choices to a very pragmatic approach rather than one following any strict Normal Form.
For my money, make sure you understand 3NF and it’s benefits so that you know what trade-offs you are making when the limitations of SharePoint require a different approach. After all, lists are not mean to be subsitutes for database tables.
(Note that SharePoint forces you into an Entity Attribute Value model, with the ability to put a little bit of fancy data entry controls over the top, so you don’t have to decide what data model to use, all focus should be on getting the best user interface from what you are given)