Key-value-pair tables have basically only two columns: A key and a value for that key. Such tables offer great flexibility for an application, as new keys (= attributes) easily can be added, without the need to change the structure of the table. Any content can be stored in the value column, as it is of type text.
What is amazing for application developers, can turn out as a nightmare for report developers: Most Business Intelligence tool needs attributes in dedicated columns (with the right data type) to allow for aggregations. This means that the table has to be pivoted.
In this talk, Markus will show a solution he implemented for a client and successfully runs in production. He semi-automated pivoting and the assignment of the right data type and will show how to achieve this in either Power Query (self-service BI) or SQL database (enterprise BI).