@JzInqXc9Dg Attribute relationships let you set up hierarchies on a dimension. If you define one as the parent of another then you can create a drill-down path. You can define them as tight or loose (quite useful for SCDs where the parent of an attribute might change over time).
@JzInqXc9Dg If the underlying tables have an actual foreign key relationship then you can mark this up on the data source view, and then that relationship can be made available to your dimension. However, this will only work if the tables can be joined at the database level.
If the table will only join to the fact table (directly or through some other path) then it can be set up as another dimension (if it's not already)
Note that attribute relationships live at the cube level - the DSV is an underlying metadata layer that can be used to mark up mappings and joins in the underlying database used to populate the cube. Once they're available in the DSV then the dimensions and fact tables can see them.
@ConcernedOfTunbridgeWells How do I "mark this up" on the DSV?
They can indeed be joined on the database level. I can do it manually with SQL in SSMS
It's just adding a "new relationship" correct?
If so, I have done that. And the field does indeed become available to my dimension. However, processing fails after this. Duplicate key - or if i reverse the relationship it fails (cant remember the error at the moment)
Altho the fields i can use for joining on the db level aren't actual keys. They are varchar fields that do happen to join correctly. not sure if that matters..
in one Dim table is a column called Dim<other table> - i use this column to join with
so it seems to be setup with that intent in the tables
@JzInqXc9Dg If the table isn't in the DSV you first have to add it, or add a named query. Then you can drag a FK relationship from the key on the parent to the FK column on the child.
@JzInqXc9Dg The key has to be unique at the source table.
well yes, i understand that. i just dont know how to resolve it
because... there should be duplicates. thats the whole point
the data structure here is not hard. i simply want this dimension to include a field from another dimension to allow filtering. i dont see why BIDS/SSAS is not letting me do so..
@JzInqXc9Dg It sounds as if your star schema is a bit broken, but that can happen. If you are absolutely sure that you are OK with duplicate values in your data source you could look into the KeyDuplicate property
However, if you get the chance to review your design at some point you might want to look into the concept of a thing called "surrogate keys" for your key attribute
Why would this question get closed as unclear? dba.stackexchange.com/q/141558/507 It was pretty specific on what the OP was asking...unless I just read into more than others.
@ShawnMelton Don't remember what my choice of a close reason was exactly. If it was the "not clear" like the majority's, I guess my issue was that the OP didn't specify the kind of access to SSCM they'd like to have.
From what I remember, I once made a typo and set SQL Max memory to half a gig and it wouldn't start properly (though it's been too long ago to remember), this guy is suggesting 300MB. Fairly confident that won't work very well
Set a maximum of 300MB per instance and be done with it. Seriously, you can monitor it with something like this to determine which may be candidates for giving a little more or less to.
SELECT DB_NAME(database_id) AS [Database Name],
COUNT(*) * 8/1024.0 AS [Cached Size (MB)]
FROM sys.dm_os_buffe...
With not start properly I mean the service was running but I could barely connect to it and not run any queries
Hmm, He's active on main, he edited an answer of mine not so long after I posted it today
OMG it's a FLOOD on main :)
Anything called a database would allow you to select more than 1K rows. Can you please add details about the database and especially the client you are using? The setting is likely to be in the client pagination. — Tom V3 mins ago
Set a maximum of 300MB per instance and be done with it. Seriously, you can monitor it with something like this to determine which may be candidates for giving a little more or less to.
SELECT DB_NAME(database_id) AS [Database Name],
COUNT(*) * 8/1024.0 AS [Cached Size (MB)]
FROM sys.dm_os_buffe...
I was thinking about adding this comment.
If I only have 1 glass of water to keep 50 people alive for a week. The answer isn't to divide up the water evenly between the 50 people. We simply need to get more water or some folks are surely going to perish.
@Kin totally unrelated. we have our own in-house backup procedure that checks diff base from master_files and will cause a full backup if it's not what it expects
we had a failover yesterday and our diff backup detected a difference in the base ...
