Microsoft Updated DP-500 Exam Questions and Answers by ruairi

Refresh data from an on-premises SQL Server database

The SQL Server database must be accessed by Power BI through an on-premises data gateway.

You can install an on-premises data gateway on the same local computer as SQL Server (in production, it would typically be a different computer).

Graphical user interface, text, application Description automatically generated

Step 1: Create a parameter that contains the service root URI

Step 2: Get data from OData feed source and use the parameter to populate the first part of the URL.

The URI is in the first part of the query.

Example: let

Source = OData.Feed ("https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/WorkItemSnapshot? "

&"$apply=filter( "

&"WorkItemType eq 'Bug' "

&"and StateCategory ne 'Completed' "

&"and startswith(Area/AreaPath,'{areapath}') "

&"and DateValue ge {startdate} "

&") "

&"/groupby( "

&"(DateValue,State,WorkItemType,Priority,Severity,Area/AreaPath,Iteration/IterationPath,AreaSK), "

&"aggregate($count as Count) "

&") "

,null, [Implementation="2.0",OmitValues = ODataOmitValues.Nulls,ODataVersion = 4])

in

Source

Box 3: From Advanced Editor, duplicate the query and change the resource path in the URL.

Choose Get Data, and then Blank Query.

From the Power BI Query editor, choose Advanced Editor.

The Advanced Editor window opens.

Edit the query.

Etc.

Enable large datasets

Steps here describe enabling large datasets for a new model published to the service. For existing datasets, only step 3 is necessary.

Create a model in Power BI Desktop. If your dataset will become larger and progressively consume more memory, be sure to configure Incremental refresh.

Publish the model as a dataset to the service.

In the service > dataset > Settings, expand Large dataset storage format, set the slider to On, and then select Apply.

Enable large dataset slider

Invoke a refresh to load historical data based on the incremental refresh policy. The first refresh could take a while to load the history. Subsequent refreshes should be faster, depending on your incremental refresh policy.