When the Designer generates a denormalized view, it creates one view and puts all elements of the hierarchy into the view. All the elements in a denormalized view belong to the same parent chain. Denormalized views, like denormalized tables, generate duplicate data.

The Designer can generate denormalized views for XML definitions that contain more than one multiple-occurring element if the multiple-occurring elements have a one-to-many relationship and are all part of the same parent chain.

The following figure shows a DTD file that contains multiple-occurring elements, in this case Product and Sales:

Product and Sales are multiple-occurring elements. Because the multiple-occurring elements have a one-to-many relationship, the Designer can create a single denormalized view that includes all elements.

The following figure shows the denormalized view for ProdAndSales.dtd in a source definition:

The Designer creates a single view for all the elements in the ProdAndSales hierarchy. Because a DTD file does not define datatypes, the Designer assigns a datatype of string to all columns. The denormalized view does not need a primary or foreign key.

The following figure shows a data preview for the denormalized view: