![]() ![]() The screens are a bit different in Visual Studio 2017, but the concept is the same. I also wanted to note, this can also be done in Visual Studio 2017. Using this to piggy back on multiple cubes could cause some dependency issues if other cubes fail to process, or are deprecated over time. As with any technology and feature, it has its place to be used. Overall, this seems like a great feature that should have some interesting uses. It also means that there is no need to build yet another fact table in your data warehouse for feeding data into your cube. This means less memory will be used as opposed to pulling in the full sales fact from my Sales cube. Since my query returns aggregated data based on the level of granularity I built the query at, my sales table in my Forecast cube only has 468 rows. The other interesting find is the fact table for my sales cube has 60,855 rows. ![]() It seems the query only runs when the cube is being processed which means there should be very little impact on the server. When I browsed my Forecast cube, the data was still pulling through. If it was, that could be a substantial impact on the cubes and server. After processing, I cleared out the data from the sales cube that I performed the MDX query on to see if the query was doing a live query every time I queried against the Forecast cube. As you can see, it simply has a sales fact, a product dimension, an employee dimension, and a date dimension.Īfter I published, there were a few things I was curious of and explored a bit further. Let’s take a look at my sales cube schema. This does not work, though, if I want to compare the data side by side in the same report. In this situation, I want to look at a comparison of the two data sets. ![]() This is fine if I want to look at just sales information or just forecast information. With Power BI, I can only connect to one Analysis Service at a time. I have a sales cube (DemoOlap) and a forecast cube (DemoMdxTableOlap). I thought I would share what I discovered while working with this concept.įor this blog post I made a new solution in Visual Studio 2019 that contains two SQL Server Analysis Services Tabular cubes. I thought this was a very interesting concept, but there wasn’t much documentation I could find on how to do this. It seems like an easy enough solution, but is it really the way to go?Īfter some digging around the web, I found that you can create tables from other cubes. My first thought was to just build the new cube and then add the already existing fact table into my new cube. Recently I was working on a project where I was building a Tabular cube that needed to have information in it that was in an already existing cube. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |