After creating our Parent-Child dimension (Part 1), we will see in this second part, the different properties of this dimension.
For this, we keep the same example as before : the dimension of the families (Categories) of a product organized according to a descending hierarchy.
Let's go !!!
Read More Parent / Child Dimension Properties - Part 2
Parent-Child dimension is a type of dimension that I did not know before (yes we can not know everything ☻), but I had the opportunity to use it within the framework of a project on which I worked; suddenly, I said to myself that it will be a good idea to share with you what I learned about this dimension.
In order to better explain how to create this type of dimension and the options, you need to understand the context of the example which is part of this article.
Read More The Parent / Child dimension - part 1
Here we are in the 2th part of this article where there is less blah blah but more practice (putting our hands in the leg !!)
In this part, I will explain the step by step operations to create the cube partitions in a dynamic way.
First, prepare the test data, for that, we will work with the database and the cube AdventureWorksDW, you can download the sources as well as the deployment scripts from the links below:
Read More Dynamic management of SSAS partitions - part 2
Working on a data warehouse at a high volume can cause us performance problems to process or query the SSAS Cube.
To remedy this kind of problem, you will have to partition the cube, but not just any old way, you really need to have a well-defined dynamic SSAS partitioning plan.
Let's see how we can design this plan in a BI project ☻
Before starting the implementation of this partitioning plan we will talk in this 1ère part of this article on the advantages and disadvantages of SSAS partitioning.
Read More Dynamic management of SSAS partitions - part 1
The use of a parameterized query in a lookup makes it possible to lighten the cached data, especially in the case of iterative processing, and that we do not need to load all the data in the cache.
Even if the lookup component does not offer the possibility of using variables but it does have the property SqlCommand which allows to specify the lookup request and which can be configured.