There is a direct SQL connection (to the TDS endpoint) So, assuming SSRS has been covered so many times and you probably know what’s doable with SSRS, let me cover some of the Power BI Paginated Reports features.
Most likely, if you are thinking of getting SSRS reports developed, you’ll need to start paying the developer, and this is not cheap either, so, in the end, if you tried comparing licensing fees only, it might not give you an accurate picture. This is not to say that Power Apps licensing in general is cheap these days, and this is not to say that everybody can develop SSRS reports. That last one can be a big deal if you are thinking of switching to Power BI Paginated Reports, since the first thing you’ll probably realize is that you need a Premium Power BI workspace.Ī Premium Workspace will cost you, quite a bit. Meaning that it comes with model-driven apps. That said, we have to use FetchXML to build those SSRS reports, and that kind of limits us in terms of the capabilities, since FetchXML, even though quite powerful, does not offer the same capabilities as SQL.Īnd SSRS is “free”. However, we can go to the model-driven app and run reports from there. SSRS will run on the reporting server, and, as far as model-driven applications go, it’s always been the case that reporting server would have been hidden from us, developers. Although, it will probably look surprisingly familiar to anyone who had some experience with SSRS: Unlike SSRS, Power BI Paginated Reports are supposed to be designed using a tool called Power BI Report Builder. They are both meant to deliver pixel-perfect reports, and, actually, Power BI Paginated Reports are using the same “rdl” format as SSRS. To start with, both are somewhat the same. So, how do Paginated Reports fair against SSRS? Now that SSRS authoring tools have finally been updated (and there is a great article Nick Doelman published the other day on this topic), it might be the right time to ponder on which technology we should be using moving forward since there are two now:
0 kommentar(er)
