I unfortunately don't know of a more elegant way, and have used empty script tasks in the past as a starting point.

You'll probably have to do something like this: https://docs.microsoft.com/en-us/analysis-services/tutorial-tabular-1200/supplemental-lesson-implement-dynamic-security-by-using-row-filters?view=asallproducts-allversions

To an extent, yes. Some tools, as good as they are, require a lot of monotonous and repetitive work and we're new seeing tools in some of those cases that...

BIML is that free tool. Use BIML Express in Visual Studio.

BIML could be your friend in this case, to generate all of these packages and save your sanity.

Ok gotcha, so it's really only the lookup for existence that's an issue.

How about assigning surrogate keys in your destination table, and then building either filtered indexes or partitioning the...

From a partitioning point of view, just think of a way in which you can structure your source query to get a somewhat equal distribution. Dates work well for this,...

You could try to partition the import and load the cache in parallel, but I have never done that and don't know if that will really eliminate the problem.

To be...

You can use AD Groups in Analysis Services roles to limit data, but row-level-security is to limit data from the end user and not entire entities (tables) or attributes. There...

You can use the following API to refresh a dataset: https://docs.microsoft.com/en-us/rest/api/power-bi/datasets/refreshdatasetingroup 

Here's a C# example on the .Net object model you can use to call the API: https://docs.microsoft.com/en-us/power-bi/developer/automation/walkthrough-push-data-complete-code

I'd recommend using Powershell, as it is much more robust than trying to do it in native SSIS tasks.

I like to use XMLA directly in the SQL Agent jobs. At least in my experience, the built-in SSAS processing task is a little clunky sometimes.

No worries. The dimension that was failing was most likely causing your other dimensions down the list not to process, and SSIS wasn't throwing the error like it should have....

In the world of multidimensional cubes, the value it's complaining about is usually the culprit (or part of it). I would do the following:

• Fully process the dimension in question

...

If the cube is processed "full", then all associated measure groups in the cube will also be processed. You may have to dive into the error a little more. For...