Report Builder does not allow developers to refer to SSRS catalogued reports that include user credentials – only reports from publicly available data sources are supported.
That is, if the data source authenticates using the Security Support Provider Interface (SSPI), the same credentials are transmitted to SQL Server as if the user accessed the report from a Windows browser window. Note that the connection string defined in the data source must contain the same credentials to access the data. The most important difference between Report Builder and SSRS is that the connection to the database is made through the remote client report processor, not through the server-side SSRS report processor.
However, unlike the SSRS service which returns HTML code to a browser, the Report Processor module of the Report Builder performs these steps on the client system and creates a report in the Report Builder window. This is the same sequence of events that the SSRS handler performs on the server when visualizing simple reports. when exceptions occur, displays warning dialog boxes for the user.performs built-in queries and passes a set of lines to the report handler combines data with the report layout from the report definition to the RDL.responds to unfilled input parameters by displaying dialog boxes.
Report Builder 2.0 is based on the SQL Server 2000 Reporting Services (SSRS) code.
I'm amazed at how limited SIMS reporting for a product so widely used as an MIS. At least ISAMs and Bromcom (for example) get that some customers have different needs so give you a reporting engine that is relatively accessible but then make available more advanced methods without you having to shell out for the prvillige. You'll be better off going "pfff, SSRS was so 3 years ago, it's all PowerBI now" then buy a SIMS > PowerBI connector and use that \ SIMS reporting engine.If my MIS wasnt fulfilling reporting requirements and was expensive in comparison to alternatives I'd be questioning if it was fit for the purpose rather investing further funds in other solutions to do the job for the MIS.
Capita won't support you (write stored procedure to use in your SSRS report) and I doubt you'll find a cost effective solution. You won't be able to train someone in a few weeks to know SSRS and SQL to the required level.