Issue Summary

In Enterprise Insights, the table [Jira Board] contains duplicate columns for [Team ID] and [Program ID], with one set prefixed as "FK" and another without the prefix. These columns are foreign keys in the schema, so the prefix "FK" should consistently be used. Additionally, confusion arises due to the presence of duplicate views named [Jira Board] and [Jira_Board] (with an underscore), which present inconsistent representations of these columns.

Steps to Reproduce

1. Access the Enterprise Insights by using any SQL Client (for example, Azure Data Studio)
   1. Check the columns of the [Jira Board] table;
   2. Check the table [Jira_Board]

Expected Results

• In the [Jira Board] table, the columns [Team ID] and [Program ID] should appear only once, consistently prefixed with "FK" to accurately represent their Foreign Key status.
• The duplicate views [Jira_Board] in both current_dw and export_dw schemas should not exist to avoid confusion and redundancy.

Actual Results

• The [Jira Board] table presents [Team ID] and [Program ID] twice: once with the "FK" prefix and once without it.
• The views [Jira_Board] (with an underscore) exist in both the current_dw and export_dw schemas, where [Team ID] and [Program ID] appear without the "FK" prefix.
• This inconsistency confuses users and misrepresents the schema design.

Workaround

• Users manually verify the schema definitions to determine the correct columns and Foreign Key representations.
• Duplicate and incorrect data require additional effort for validation and filtering during analysis, increasing the risk of errors.