cube

问题 Having built a few "test" datacubes through using VS2017, my team are now ready to start working with them in a more production like manner. As such there are a few basic tasks that we need to implement, but we are struggling to find useful resources for. How can we do a monthly refresh of the cube without regenerating all of our dimensions and fact tables? Does VS2017 recognise/honour Slowly Changing Dimensions if we implement them in our Dimension design? To have a guess at this: In our ETL

问题 I stumbled upon a problem which I cannot resolve. For my academical project I have a cube representing an airline's data warehouse. In this airline, passengers fill out a qustionnaire with 5 questions, rating various aspects of the flight from 1 to 10 I was asked to write an MDX query to show how their overall grade of the flight ( average of five grades ) depending on the class they were in. This is my query: WITH MEMBER [Average Grade1] AS [Measures].[Grade1] / [Measures].[Flight Count]

问题 I need to build a local .cub file for my Excel-using clients. I have scrounged together some VB code but it fails : ConnLocation = "LOCATION=C:\test.cub;" ConnDSN = "SOURCE_DSN=DSN=TEST;UID=test;PWD=pass;" ConnCreateCube = _ "CREATECUBE=CREATE CUBE [TestCube] (" & _ "DIMENSION [account_code]);" Connection = CreateObject("ADODB.Connection") Connection.Provider = "msolap" Connection.ConnectionString = _ ConnLocation & _ ConnDSN & _ ConnCreateCube I have trimmed this down to the above code and

问题 I am quite new to SSAS, so please forgive me if there is an obvious answer to my question - I have done a lot of research today and cannot find the answer myself. I am trying to apply Dimension Data security (in a SSAS DB role that I have created) to my SSAS 2012 cube. Essentially, what I am trying to do is that users assigned to the role that I have created, should not be able to see any data for a specific dimension member. So, when I edit the cube in SSDT (SQL Server Data Tools or Visual

问题 I am new to OLAP, and figured out how to make a cube and process it. However, when i play with it too much, i eventually come up against this error: Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_v_MYEntities, Column: uniqueId, Value: 2548. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Unique Id of Dimension: v MY Entities from Database: Test Cube New, Cube: MYdm MyApp - Views, Measure Group: v

问题 I'm currently implementing a mesh extrusion algorithm for plane shapes, let's assume for a rectangle. When I extrude this rectangle I create four new sides (resulting in 8 new triangles) and a new bottom for the 3d shape. This works fine when I duplicate all vertices so that my final cube has 24 of them. But I'd like to avoid these extra vertices now so that I have only 8 vertices. Unfortunately, in this case I do not know how to calculate the UV coordinates and I keep getting wrong results

问题 The task is to automate OLAP pivot table data filtering. There are some items in pivot field named sPivotFieldName I need to exclude. The code below works pretty fine. With Worksheets(sWorksheetName).PivotTables(sPivotTableName) With .CubeFields(sCubeFieldName) .Orientation = xlRowField .IncludeNewItemsInFilter = True End With .PivotFields(sPivotFieldName).HiddenItemsList = vSomeItemsToExclude End With But the problem appears when I'm trying to change cube field ".Orientation" property's

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 5 years ago . We are designing a dimensional model for an IT support business. There are cases (some call them tickets or incidents) with different statuses (feels like an SCD type II dimension) We also need to consider the count of cases and SLA time duration as measures. Before going into

问题 Hi i'm struggling with adding time dimension to OLAP cube. I can get everything in cube to work except date. In my source data view I have datetime column. I go by using Dimensions->New Dimension-> Generate time dimension on the server . I end up with a nice hierachical time dimension (Date-Month-Quarter-Year). Later I add this dimension to cube and define regular relationship with datetime column from source data view (same table which has fact data). When I try to deploy the cube, I get

问题 This is an error message I get after processing an SSIS Cube Errors in the back-end database access module. The size specified for a binding was too small, resulting in one or more column values being truncated. However, it gives me no indication of what column binding is too small. How do I debug this? 回答1: Open your SSAS database using SQL Server Data Tools. Open the Data Source View of the SSAS database. Right click an empty space and click Refresh A window will open and show all changes