How do I need to handle a case in which the fields in a fact table that represent the foreign keys to the dimension tables might change? What kind of process do I have to do to the cube?
View Complete Post
Scenario: Bank Accounts and Customers. One Account can have many customers and many customers can have one joint Account. so its Many to Many relationship.
Special Scenaio: Bank provide us daily snapshot of all thier dimensions and facts, every night thier ETL run, and newsnapshot is available, previous is gone.
I am using SCD Transformation to update the dimensions, Type 1 for all the columns.
Tables1: DimAccounts (AccountsID(PK))
Table3:DimBridge (AccountID (FK), CustomerID(FK), RelationShip (varchar10))
Question1: Are we supposed to treat bridge tables as Dimensions or Facts?
Question2:If it is to be treated as Dimension, How would I apply SCD Wizard to it, Since there are two business keys involved?
Question3: Do i need surrogate key in Bridge Table, like i have in other dimensions?
I have one dimension table with over 600 item, but in my fact table only 40 of this member have lines (my fact have a filter for the 2 laste year)
How save on the dimension only this 40 members?
The ForeignKeyName attribtute of a relationship is greyed and empty when I edit a relationship of a data source view in SQL Server 2008 BIDS. How can I edit it?
I am trying to build a custom BI report with filter parameters. One thing I need to do is get the list of valid parameters for each dimension attribute. For example, the report includes the County attribute as one of the grouping attributes and
users need to be able to filter by county. When I generate the list of county checkbox/dropdown options in my ASP.NET page, I need to only list those counties which are referenced in the fact table. There is no reason to list a county as a filter
option if there are no associated facts. Essentially I am doing a inner join between a single dimension and the fact table, and then grouping by the attribute that I want to present as parameter choices. The below options are what I've tried.
I am hoping for suggestions on a better way to do this or maybe improve the performance of the option using an MDX statement. I feel like I should be querying SSAS for the attribute information instead of querying the underlying tables directly.
If anything in my SSAS cube changes that would affect the attributes used in the report, then I will have to be careful that I update views as necessary to make sure the right columns/keys are queried.
1) I tried using a group by LINQ against Entity Framework model, but that is very slow because of the way Linq uses subqueries and distinct to imple
This is quite difficult for me to communicate so please bear with me.
I have created my data source view in my solution. I have a central fact table surrounded by the dimensions. Several of the dimensions have dates which I converted to integers. Thinking that I would need separate date dimension tables so the date integers
could find their dates I created a data dimension table "snowflaked" to the dimensions with dates.
An example is my dimPolicy table has dates of creation and ending.
I converted these to integers.
A table called dimPolicycalendar was made in the DSV and then linked. A dimension snowflaked to a dimension.
When I went to create a dimension for Policy it auto attached the dimPolicyCalendar. Then all my dates disappeared. And the generic values in the dimPolicyCalendar appeared.
HELP HELP HELP PLEASE!!!
How do I get my values back?
If I wasn't supposed to add a calendar table to the dimension how will I convert those integer values to the date values I want?
I am panicking a little because I can not find any helpful resources.
You are my last hope before we are pushed to an Oracle solution. Yuck!