This is a slowly changing dimension scenario. Your implementation depends on whether or not you want to record history (broadly speaking a Type 2 SCD) or not (broadly speaking a...

This is probably caused by some sort of MDX failure/incompatibility/Excel read error.

The cell that is meant to be showing a value:

1. Is is a calculated measure?

2. Does it have a...

Tru Dat ? 😀

Depending on how your instance is set up, you can find this information in a number of places. Have a look at the following article: http://blogs.msdn.com/b/as_emea/archive/2012/01/02/initial-data-collection-for-troubleshooting-analysis-services-issues.aspx

I think you're on the right lines 🙂

I don't think that you need a "FactPatient" table in your underlying data since it looks like it's entirely dimensional. Rather, when it...

srinivas.sqlbidev (10/14/2015)

---

I know those are genuine duplicates , but users don't want to see those repetitions.

There is one more column called SalesShipToCity that they need to have as member attribute.

So...

As I said, to include the line (or row) number you would have to pre-prepare your flat file before it hits the DFT.

To get the column name is a bit fiddly but possible (unless you have a time machine and are using SQL 2016 where it's been made simple finally[/url]. Also, who...

Firstly, you have already fixed this in one way:

If I make a composite ColumnKey for CustomerName as ( CustomerName + CusomerNumber) it works but Same CustomerName Scott appears Multiple times

at...

I'm not totally sure on this (I abandoned the SSAS data mining suite in favour or RStudio and Rattle due to it being quite underwhelming) but you could probably try...

I believe that Sets do not evaluate CURRENTMEMBER in the query context so it's a bit like trying to sum to everything in a dimension.

Just do the following:

MEMBER [Measures].[Sales...

I'm pretty sure you can do what you need using IF and/or SWITCH. Lot's of stuff out there for this:

https://msdn.microsoft.com/en-us/library/gg492166.aspx

https://msdn.microsoft.com/en-us/library/ee634824.aspx

http://www.powerpivotpro.com/2012/06/dax-making-the-case-for-switch/

http://sqlmag.com/sql-server-analysis-services/ssas-tabular-part-4-deep-dive-dax

OBJECT_TYPE in the DISCOVER_CALC_DEPENDENCY DMV shows what type of column (including calculated) it is.

You can use SSAS DMVs to get this information: https://msdn.microsoft.com/en-us/library/hh230820.aspx

Hi Mikel,

This has been covered before on these boards: http://www.sqlservercentral.com/Forums/Topic1065481-17-1.aspx

SSAS won't just "know" about SCD2, you have to tell it and ensure that your logic is in place.