Shared Datasets have been round for fairly some time now. In June 2019, Microsoft introduced a brand new characteristic known as Shared and Licensed Datasets with the mindset of supporting enterprise-grade BI throughout the Energy BI ecosystem. In essence, the shared dataset characteristic permits organisations to have a single supply of fact throughout the organisation serving many reviews.

A Skinny Report is a report that connects to an current dataset on Energy BI Service utilizing the Join Reside connectivity mode. So, we principally have a number of reviews related to a single dataset. Now that we all know what a skinny report is, let’s see why it’s best follow to comply with this strategy.

Previous to the Shared and Licensed Datasets announcement, we used to create separate reviews in Energy BI Desktop and publish these reviews into Energy BI Service. This strategy had many disadvantages, similar to:

• Having many disparate islands of knowledge as a substitute of a single supply of fact.
• Consuming extra storage on Energy BI Service by having repetitive desk throughout many datasets
• Lowering collaboration between knowledge modellers and report creators (contributors) as Energy BI Desktop will not be a multi-user utility.
• The reviews have been strictly related to the underlying dataset so it’s so arduous, if not completely unimaginable, to decouple a report from a dataset and join it to a special dataset. This was fairly restrictive for the builders to comply with the Dev/Check/Prod strategy.
• If we had a reasonably large report with many pages, say greater than 20 pages, then once more, it was nearly unimaginable to interrupt the report down into some smaller and extra business-centric reviews.
• Placing an excessive amount of load on the info sources related to many disparate datasets. The state of affairs will get even worst after we schedule a number of refreshes a day. In some circumstances the info refresh course of put unique locks on the the supply system that may doubtlessly trigger many points down the highway.
• Having many datasets and reviews made it more durable and costlier to keep up the answer.

In my earlier weblog, I defined the completely different parts of a Enterprise Intelligence resolution and the way they map to the Energy BI ecosystem. In that put up, I discussed that the Energy BI Service Datasets map to a Semantic Layer in a Enterprise Intelligence resolution. So, after we create a Energy BI report with Energy BI Desktop and publish the report back to the Energy BI Service, we create a semantic layer with a report related to it altogether. By creating many disparate reviews in Energy BI Desktop and publishing them to the Energy BI Service, we’re certainly creating many semantic layers with many repeated tables on prime of our knowledge which doesn’t make a lot sense.

However, having some shared datasets with many related skinny reviews makes quite a lot of sense. This strategy covers all of the disadvantages of the earlier growth methodology; as well as, it decreases the confusion for report writers across the datasets they’re connecting to, it helps with storage administration in Energy BI Service, and it’s simpler to adjust to safety and privateness issues.

At this level, chances are you’ll suppose why I say having some shared datasets as a substitute of getting a single dataset masking all points of the enterprise. That is really a really attention-grabbing level. Our purpose is to have a single supply of fact accessible to everybody throughout the organisation, which interprets to a single dataset. However there are some situations wherein having a single dataset doesn’t fulfil all enterprise necessities. A standard instance is when the enterprise has strict safety necessities {that a} particular group of customers and the report writers can’t entry or see some delicate knowledge. In that state of affairs, it’s best to create a totally separate dataset and host it on a separate Workspace in Energy BI Service.

Choices for Creating Skinny Studies

We at the moment have two choices to implement skinny reviews:

• Utilizing Energy BI Desktop
• Utilizing Energy BI Service

As all the time, the primary choice is the popular methodology as Energy BI Desktop is at the moment the predominant growth device accessible with many capabilities that aren’t accessible in Energy BI Service similar to the power to see the underlying knowledge mannequin, create report stage measures and create composite fashions, simply to call some. With that, let’s shortly see how we will create a skinny report on prime of an current dataset in each choices.

Creating Skinny Studies with Energy BI Desktop

Creating a skinny report within the Energy BI Desktop may be very simple. Observe the steps under to construct one:

1. On the Energy BI Desktop, click on the Energy BI Dataset from the Information part on the House ribbon
2. Choose any desired shared dataset to connect with
3. Click on the Create button

4. Create the report as ordinary

5. Final however not least, we Publish the report back to the Energy BI Service

As you’ll have observed, we’re related reside from the Energy BI Desktop to an current dataset on the Energy BI Service. As you possibly can see the Information view tab disappeared, however we will see the underlying knowledge mannequin by clicking the Mannequin view as proven on the next screenshot:

Now, allow us to take a look on the different choice for creating skinny reviews.

Creating Skinny Studies on Energy BI Service

Creating skinny reviews on the Energy BI Service can also be simple, however it’s not as versatile as Energy BI Desktop is. As an example, we at the moment can’t see the underlying knowledge mannequin on the service. The next steps clarify find out how to construct a brand new skinny report straight from the Energy BI Service:

1. On the Energy BI Service, navigate to any desired Workspace the place you wish to create your report and click on the New button
2. Click on Report

3. Click on Decide a broadcast dataset

4. Choose the specified dataset
5. Click on the Create button

6. Create the report as ordinary

7. Click on the File menu
8. Click on Save to save lots of the report

That is it. You could have it. You probably have any feedback, ideas or suggestions please share them with me within the feedback part under.