Jayanth_Kurup (8/13/2015)
I should have been more clear about my points , sorry . My point revolve around the self service aspects of MSBI.Its more difficult to implement singlesignon in SSRS than in Sharepoint , the only time its gets better for SSRS is when authenticating over untrusted domains. Also with SSRS you can embed within a report viewer control and be done unlike a standalone C# app, most reporting I have seen happens over the browser.
My experience has been that getting people into SSRS Report Manager using their Windows Account is simple, I.e. no work required other than having everything joined to a domain. Now, getting a SSRS Data Source configured to use the report runner's credentials and have that work all the way from the client through SSRS and on to the SQL Server, that is another challenge entirely and has proven very difficult at times due to the complexity of configuring Kerberos delegation. That said, I find it far more difficult to get full-stack SSO and Kerberos working for a SharePoint farm than a standalone SSRS instance.
PowerBI is available in sharepoint which can use SSRS as a dataset and since the end goal is to achieve good looking reports its definitley something to consider when looking at pros and cons of Sharepoint and SSRS
Power BI is not a SharePoint-only technology. You can use Power Query in a standalone copy of Excel 2013 and source data from and SSRS report. Not sure if Report data sources are there in the Power BI Designer yet. While I haven't tried it I am pretty sure you can reference a report hosted in SharePoint as a data source too once you figure out how to craft the URL.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato