Assume that you use a calculated table that summarizes the dataset in a partition query in Microsoft SQL Server 2014 and 2016. In this situation, you may experience a circular dependency in the following scenarios:
- The column names in the calculated table are the same as the names in the summarize function, and the related tables have a many-to-one relationship to the calculated table.
- The calculated table is related to the tables that are part of the summarize function. For example, you have Table B that is related to the calculated table. There is a column name in Table B that matches a column name in one or more tables that are part of summarize function.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.