My company is trying to decide which one would be better, creating a report model off of relational tables, or using an AS cube. right now, I use Visual studio for report development. but a big part for the users is Ad-hoc reporting. What are the ups and downs of both (AS cube and Relational table, report model (Ad-hoc). And what would you suggest Any info would be helpful. Thanks!
Whats better for Ad Hoc reporting, Relational or AS Cube
Hot Topic
- Performance and Execution Plan
- permissions granted to an application intead of a user
- Error on custom data mining plugin: content type mismatch
- Failed to Open Rowset Error in Crystal Reports
- Question in sercive broker
- How can I set constant padding between the columns of the Column Chart(stacked column sub-type)?
- Validating a Source File
- Problem appending to a raw file
- Is capturesql the only way to script a drop using smo?
- SQL 2005 Transact-SQL Full Outer Self Join
SQL Server
- Can you please help me on this?
- Help!!!!--Problems about the multi column report!
- Dimensions, Table Joins, and Missing Elements
- ole db source query assistance requested
- Does MS have a glossary of terms?
- MMSQL 7.0 on MMC
- Licensing sql express for web hosting providers
- Error on Creating publication
- date parmeter converts into drop down
- Loops and building comma delimited strings
Whats better for Ad Hoc reporting, Relational or AS Cube
Chris Lively
Hi,
This question is difficult to answer without knowing the type of database you are connecting to. Cubes give advantages when you need to have a lot of drill down functionality and when a lot of calculations needs to be done. This is because cubes contain precalculated values so that when the user performs a query, not all calculations needs to be done. This will increase performance.
The main advantage of connecting to relational tables, is that you have real time data. Since cubes need to be build on a regular basis, the data is not realtime.
Greetz,
Geert
Geert Verhoeven
Consultant @ Ausy Belgium
My Personal Blog