not quite what I'm suggesting... I think that path would end up in the same place you're at now. I'm saying create a stored proc in the Source DB, in...

if you're determined to use SSIS Data Flow, one more iteration to try is creating a Stored Proc that only does the SELECT and put that in the OleDB source

Is that your drill to or drill from report in the screenshot? that button will only appear on the report you drill to when you've gotten there from the drill...

if you're trying to get that parallelism from the source you'll need 8 copies of the oledb src using modulo that are something like-

OLEDB Src 1: SELECT * FROM table WHERE Id...

If the tables are on the same SQL Server instance, you're probably better off creating SPs to do the inserts and using SSAS ExecuteSQlL tasks to call them. If you...

Use the back button that appears near the paging buttons on both Data Tools and Report Manager

does that Key value exist in your Dim table/named query?

this should do it. maybe make it into a Funtion

DECLARE 
@TestNumberdecimal(4,1) = 28.7
,@PreferredDecimaldecimal(4,1)= 0.7
;

SELECT 
CASE WHEN @TestNumber - FLOOR(@TestNumber) >= @PreferredDecimal THEN CEILING(@TestNumber) ELSE FLOOR(@TestNumber) END 
;

SET...

when you right-click -> Properties on the Project in SSDT Solution Explorer, you should see the options under Deployment. TargetDatasetFolder will just have Datasets but you can change it to...

By default, they all go the same place but you can change the target folder for datasets and sources from the properties on each project in SSDT.

There's also this tally table approach if the col3 source can be longer 100 and up to 5000. 

  DROP TABLE IF EXISTS #tmpExamples ;

WHERE LEFT(a.Column,3) <> 'V21'

ISNULL(