Home/ Questions/Q 237295
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T20:24:50+00:00

I’ve just begun diving into data warehousing and I have one question that I

  • 0

I’ve just begun diving into data warehousing and I have one question that I just can’t seem to figure out.

I have a business which has ten stores, each with a certain employees. In my data warehouse I have a dimension representing the store. The employee dimension is a SCD, with a column for start/end, and the store at which the employee is working.

My fact table is based on suggestions the employees give (anonymously) to the store managers. This table contains the suggestion type (cleanliness, salary issue, etc), the date it was submitted (foreign keyed to a Time dimension table), and the store at which it was submitted.

What I want to do is create a report showing the ratio of the number of suggestions to the number of employees in a given year. Because the number of employees changes periodically I just can’t do a simple query for the total number of employees.

Unfortunately I’ve searched the web quite a bit trying to find a solution but the majority of the examples are retail based sales, which is different from what I’m trying to do.

Any help would be appreciated. I do have the AdventureWorksDW installed on my machine so I can use that as a point of reference if anyone offers a suggestion using that.

Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The slowly changing dimension should have a natural key that identifies the source of the row (otherwise how would it know what to compare to detect changes). This should be constant amongst all iterations of the dimension. You can get a count of employees by computing a distinct count of the natural key.

    Edit: If your transaction table (suggestion) has a date on it, a distinct count of employees grouped by a computed function of the suggestion date (e.g. datepart (yy, s.SuggestionDate)) and the business unit should do it. You don’t need to worry about the date on the employee dimension as the applicable row should join directly to the transaction table.

    • 0