The query is behaving as expected. You are returning both Level 3 and Level 4 attributes on the query axis, and because your attribute relationships are configured the way they...

From the above, I'm guessing that your attribute relationships also follow the same structure as your hierarchy. If my assumption is correct, then your query will always return two rows...

Not quite the case that it's free for commercial use.

While you can assign the free license to everyone in your organization, that free license does not give...

Excel is known for running less-than-ideal queries when it comes to cubes. Instead of just blindly throwing more resources at it, I would suggest looking at the query that's being...

According to BOL:

<SELECT query axis clause> ::=  [ NON EMPTY ] Set_Expression  [ <SELECT dimension property list clause> ]   ON     Integer_Expression    | AXIS(Integer)    | COLUMNS    | ROWS    |...

Your script task will of course work, but I am not sure that you're really making maintenance any easier...you're just moving it around to a different place. Arguably it would...

You can't have it both ways. If you force the execution result, then the OnError event will of course not fire. If you want the SQL job to succeed, I'd...

See the following: https://docs.microsoft.com/en-us/sql/integration-services/security/access-control-for-sensitive-data-in-packages?view=sql-server-2017

You also have to provide the password when executing the package, otherwise it will fail.

You can try the format() VBA function (https://docs.microsoft.com/en-us/sql/mdx/vba-functions-in-mdx-and-dax) or the FORMAT_STRING MDX function (https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/mdx/mdx-cell-properties-format-string-contents)

Yes, all of this is possible in SSIS. Describing the steps would not be much different to what you have listed here, so why don't you start with the development...

Could it be that this variable had a different type before? You may have environment(s) configured on your Production instance that are assigning a non datetime value to this variable.

You would think (hope) that will be the case, but I'm not sure that it uses the same platforms to gather data. I would be inclined to use the system...

Could it be that your packages aren't logging at the required granularity?

Scott, would you mind giving the following a try: Make the parameter a text data type, and make sure it has a valid default value. See if that helps the...