Tag Info

Hot answers tagged

9

HOW TO DO THIS WITH T-SQL: As requested this is an alternative to my previous answer that showed how to do it per-user with Excel. This answer shows how to do the same thing shared/centrally using T-SQL instead. I do not know how to do Cubes, MDX or the SSAS stuff for this, so maybe Benoit or someone who does know that can post its equivalent... 1. Add ...


7

HOW TO DO THIS WITH EXCEL Here's how I would do it in Excel... 1. Add SalaryRanges Excel Table Insert a new worksheet, call it "Salary Ranges". In row one add the text headers "Min", "Max" and "Range" in that order (should be cells A1, A2, A3, respectively). In cell B2 add the following formula: =IF(A2="","",IF(A3="","+",A3-1)) In cell C2 add this ...


3

With the MDX language you can create custom members that will defines the ranges. The following expression defined a calculated member that represents all the salaries between 501 and 1000: MEMBER [Salary].[between_500_and_1000] AS Aggregate(Filter([Salary].Members, [Salary].CurrentMember.MemberValue > 500 AND [Salary].CurrentMember.MemberValue <= ...


2

That's right. The cube browser control within SSDT is completely different to the one that used to exist in BIDS2008 or lower. This had me going at first too. The best way i found to get around this was to launch into excel, which can be done from the cube browser tab. I believe it even creates a temporary connection file for you too so you don't have to ...


1

The solution was removing the empty files E:\MSAS11.DWH_AS\OLAP\Data\Cube Fraude.0.db\MY_DATABASE OLAP.56.cub.xml which allowed the aggregation to continue


1

Oh my dear.. First of all. In your case I would like to suggest you to choose the "Process Default" option. If you are using Process Full always you are dropping all data and objects and recreating all of your stuff. You don't need them. Very often the proposal option is to use ProcessData followed by ProcessIndex. I didn't proces the cube from within the ...


1

First, I suggest you read about star schema first. Not understanding the concepts could lead to wrong results. You may use the transaction as your fact table as in the diagram below. Don't use DISTINCT, instead you want to use: SELECT ... FROM fact GROUP BY dimension data (time, transaction and bank) WHERE condition to restrict dimension data and join ...



Only top voted, non community-wiki answers of a minimum length are eligible