Dear @aftabp ,
I would recon this would work well. By excluding the tables you dont want to run you make sure that the API does not gets requested more then it should.

If you just want to run one or two table from the DSA on you could either create a new perspective which is not dynamic or just put in the table you want to run from the DSA (to MDW and semantic layer).
It just depends how any table you have which indicates how much work it is to do and maintain.

Hope this helps

= Daniel

Hi @aftabp 

I have seen that excluding complete areas makes the executions a bit slow. It checks all the tables in each part that is excluded which takes some time.

So this will work when it mainly is individual tables you exclude, but be slower when adding whole areas.

So think about the perspective you added there. It may be OK with a perspective, where I mainly have seen the issues is if you add a perspective to be excluded and then add a DWH or all semantic models in the exclude area.

@Thomas Lind 
Execuse my ignorance but by area you mean exclude the whole DSA?

The view is in DSA so wouldnt excluding DSA would also exclude the update of the view?

Or, how do you mean?

Hi @aftabp 

Yes I meant something like the whole DSA Data Warehouse. My point was that it was better to exclude individual tables compared to areas, so this setup

would be faster than this setup

This is because it does not have to read all the redundant tables in the DSA. It will read all of them and find that they are to be skipped even though they weren’t going to be executed in the first place.