Hi Power BI Community members and experts,
Any additional or have to be modified in the above steps?
Any help would be highly appreciated.
You should first have an understanding of the low-level requirements of the solution you're providing before you can make design decisions. Generally it is recommended to have a dedicated Report Server set up so resources aren't constrained.
Some questions to ask whilst scoping out your requirements:
These all use varying amounts server memory and when you have some ball park figures, make sure you add an extra amount of memory on top to account for growth.
Spec'ing out your Report Server is a crucial step you have to get right in order to avoid any project delays. This also extends to ensuring that the DW is performing optimally and returning data efficiently for the Report Server to consume in a timely manner.
Hi @Rook ..
Thanks a ton for your reply ...
below are my replies:
Thank you so much for your help!
Im assuming that the finance users will have specific access to only certain records and they can only view what they're privleged to view - correct? If this is the case, you'll need to worry a bit about how authentication will be designed within the reports.
Authentication is used for Row Level Security, if you're using an Import method you cannot take advantage of SQL Server 2016+ RLS features (Security policies and predicates) and will have to architect a more... round-about way of providing RLS, either in DW Data Model, or within the Power BI reports themselves.
Please also note, that current version of Report Server does not have the capabilities to manage user Roles for reports just yet, so expect difficulty in setting this up -Power BI Service would be better suited for this case.
This is where taking Power BI Service would be advantageous as it has more baked and ready to use features that are reguarly updated - whereas Report Server is lagging behind by several months.