Time size does not work in SQL Server Analysis Services

Question

My fact table has a Date column that I used as a foreign key for the time dimension table that I used SSAS to create in the data source. However, when I expand the cube and view it, adding the attributes of the time dimension or any of its hierarchies does not filter any of these measures. It seems like a gap between the time information in my fact table and the SSAS time measurement table for me.

Am I missing something? How can I link them so that I can use the generated time dimension to apply the slicing and dice analytics on my cube based on the date values ​​in my fact table?

Answer 1

• Is the date column the primary key column of the dimension table?
• Is this a link to a foreign key from a fact table?
• Are primary key and foreign key relationships in DSV Analysis Services?
• In the Cube editor, do you see a filled white area at the intersection of the measure group and a time dimension that displays the correct key name, and not an empty gray space?
• Does it have dates or dates?

A commonly used pattern is used to measure time in OLAP applications when you have a grain of days to have an integer primary key of the yyyymmdd structure (i.e. year * 10000 + month * 100 + day_of_month . This makes the key accessible to humans, but still is an integer that is slightly more efficient for Analysis Services.