topic Degenerated dimensions in QlikView https://community.qlik.com/t5/QlikView/Degenerated-dimensions/m-p/585040#M1326751 <HTML><HEAD></HEAD><BODY><P><BR />Hi All</P><P></P><P>Can anyone shed some light on how qlikview behaves when we have degenerated dimenions in fact table in terms of</P><P>Performance, RAM usage, reload time, qvd and qvw size.</P><P></P><P>Degenerate dimensions commonly occur when the fact table's grain is a single transaction (or transaction line).</P><P> For eg: Transaction Number is a degenerated dimension in fact. </P><P>Is it advisable to keep degenerated dimension in fact or separate it into a dimension table by replacing with key column.</P><P></P><P>Thanks in Advance</P><P>Veena</P></BODY></HTML> Mon, 26 Jan 2026 18:19:17 GMT 2026-01-26T18:19:17Z Degenerated dimensions https://community.qlik.com/t5/QlikView/Degenerated-dimensions/m-p/585040#M1326751 <HTML><HEAD></HEAD><BODY><P><BR />Hi All</P><P></P><P>Can anyone shed some light on how qlikview behaves when we have degenerated dimenions in fact table in terms of</P><P>Performance, RAM usage, reload time, qvd and qvw size.</P><P></P><P>Degenerate dimensions commonly occur when the fact table's grain is a single transaction (or transaction line).</P><P> For eg: Transaction Number is a degenerated dimension in fact. </P><P>Is it advisable to keep degenerated dimension in fact or separate it into a dimension table by replacing with key column.</P><P></P><P>Thanks in Advance</P><P>Veena</P></BODY></HTML> Mon, 26 Jan 2026 18:19:17 GMT https://community.qlik.com/t5/QlikView/Degenerated-dimensions/m-p/585040#M1326751 2026-01-26T18:19:17Z