sterlingrelocation
asked on
Integrating reporting services with analysis services.
I am looking for a possible solution. As of now, I am using SQL reporting services to create reports. The data is fetched from SQL server relational database by using stored procedure. Ours is an ASP.NET web app and so far, I have created a proper reporting engine which integrates seamlessly with reporting services. As most you know, as the reports get complex (say when it involves complicated summations etc), performance is getting a hit. To over come that, I was looking at Microsoft Analysis services (cubes). But, right now, I am kind of stuck. These are the points which really stop me from proceeding further.
1) I couldnt find enough materials in internet which talks about integrating analysis services with reporting services.
2) Is reporting services is the right front end tool for cubes?
3) Also, do I need to use SSIS or any ETL for porting the data from SQL relational database to cubes?
I am at the initial stage of my research and it could be helpful if you could give me right pointers to proceed.
1) I couldnt find enough materials in internet which talks about integrating analysis services with reporting services.
2) Is reporting services is the right front end tool for cubes?
3) Also, do I need to use SSIS or any ETL for porting the data from SQL relational database to cubes?
I am at the initial stage of my research and it could be helpful if you could give me right pointers to proceed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I like Aurci1983 idea. Performance point and Procalrity are the best options. I also used DUNDAS OLAP addin to ASP.NET(http://www.dundas.com/prod
Should note that ProClarity is being integrated into the next version of MOSS Enterprise (or whatever the heck they will call it)
I guess it was aquired by Microsoft in 2006 and it integrates with Performance Point and MOSS.
ASKER
Thanks Auric. Thats a good starting point for me.
2. Whether or not SSRS is the right front-end depends on your needs. It all depends on how much flexibility the end-user wants/needs. Excel 2007 could be an interesting option if you're going to build cubes. It can connect to a cube and the end-user can build nice pivot tables that way.
3. Theoretically you don't need SSIS but it also depends. In most cases it is interesting to first build a data warehouse with dimension and fact tables and then build a cube on top of that. Takes some of the complexity away from building cubes.
BTW: have a look at the AdventureWorks sample databases and cubes, this allows you to try it out without spending days setting one up yourself. It's available at CodePlex: http://msftdbprodsamples.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=18407