Um.
Probably the best way to think of Analysis Services is that it's the server-side equivalent of an Excel pivot table (that is, rather than the client - excel - having to do the pivoting itself from the raw data, the pivoting can be done on the server and the client only gets the results). Also SSAS still needs to get the data from somewhere, typically a separate relational database. You can handle projections in SSAS using lead/lag type functions, and reclusive calculations, but they won't perform as well as laying out the data in the right form to start with. From: Preet Sangha Sent: Monday, March 31, 2014 8:57 AM To: ozDotNet Stephen, SQL Server Analysis Cubes are essentially multidimensional spreadsheets. Preet Sangha On 28 March 2014 20:03, Stephen Price <step...@perthprojects.com> wrote: Hey all, Wondering if anyone has taken a spreadsheet and turned it into an app before? This spreadsheet has lots of data that used the previous row to calculate the new row's data (as spreadsheets often do). Was wondering how the best way to duplicate that functionality in a .Net app with classes/database. Possible ways I've thought of; 1. Class that calculates on the fly the desired row/year of data each time it needs it. 2. The spreadsheet takes some starting values and the applies a formula to each row, could do the same thing in memory in a lookup dictionary or similar so it only needs to be done once. 3. Alternatively put that data into tables in database... downside, if the initial value is changed it would have to find and modify the appropriate rows in the database. other ways? cheers, Stephen -- regards, Preet, Overlooking the Ocean, Auckland
