Your use of an intermediate dimension is ineffective in this case. A dimension attribute's key has to be unique, but yours isn't because the code is repeated. Even the surrogate...

Your syntax for the scoped assignment is incorrect.

A scoped assignment sets the value of a calculated measure(s), but in itself is not a calculated measure. This means that you cannot...

I'd do 4 separate fact tables as a start. That'll give you a little more flexibility in designing partitions, etc. and you could always combine them at a later stage....

How about this?

WITH

MEMBER [Measures].[QtyTotal] AS

[Measures].[QtyInWarranty] + [Measures].[QtyInExtension]

SELECT

NON EMPTY

{

...

You'll have to provide more information. How much data do you have? What is the partition strategy you're using, and how does that align with record counts? Do you have...

It should be possible. Can you post the structure of the dimension members/hierarchies in question as well as the measures?

Without more details about the cube it's composition and aggregations etc. and also what you are trying to achieve here, it is almost impossible to help you optimize the query.

If...

I think part of the issue is the internal use of the FLOAT data type. See this article for more information: http://www.sqlservercentral.com/blogs/richard-douglas/2013/02/01/float-datatype-casting-issue/

What happens if you use the Currency data type...

srinivas.sqlbidev (12/30/2015)

---

Thanks Martin Schoombee,

I am new to SSAS , it seems complicate to me , I am not able to understand how to implement it.

Is there any way that you...

Yes, it is possible. Have look at the following to get started:

http://prologika.com/CS/blogs/blog/archive/2009/08/19/yet-another-relative-dates-implementation.aspx

http://blog.crossjoin.co.uk/2006/04/19/handling-relative-time-periods/

According to this article (https://msdn.microsoft.com/en-us/library/hh230820(v=sql.120).aspx), the MDX query needs to have the following syntax to include restrictions:

Select * from SYSTEMRESTRICTSCHEMA ($System.<schema rowset>, <restriction parameters and values>)

I've tried it with the...

Can you post your query?

I guess the first question is why your fact table has Effective/Termination dates instead of the actual date of the activity?

Duplicate post...see here for the original thread: http://www.sqlservercentral.com/Forums/Topic1742528-364-1.aspx

Unfortunately I don't think you would find any whitepapers or conclusive sources that prove it would be best keeping them together.

Over the years I have seen it done in all...