SSMS Error when refreshing a Power BI Table: Paramter name already exists

2 weeks ago I talked about A No-Code Method to Refresh One Table From a Power BI Dataset in the Service. I recently ran into an error using this method, so I thought it was worth sharing this error, and the solution 😀, with you.

TL;DR

Don't use the initial catalog when you're connecting to a Power BI dataset with SQL Server Management Studio (SSMS).

If you want to now more details about the exact problem and solution, please read on below.

Problem

In my previous post I mentioned:

"With some tools it might be necessary to also provide the Initial Catalog (the dataset to connect to in your workspace). The datasets in your workspace will eventually show as databases under your AS-server:"

I did specifically say some tools, and might. 😁

So, to be even more specific, when using SSMS ánd the option for initial catalog, you run into the below error message:

I tried a few things before I got asked for some (external) help. A little bit of context around the problem:

• Note that the message itself also has a typo in it (paramter 😂).
• It happens to every table in every dataset (I tried so far) in this workspace. I tried another workspace and that refreshed fine from the UI.
• A colleague is getting the same error message in the UI for this particular workspace.
• Looking at the error I checked if there are params called name in the datasets, but there aren't.
• It's a test workspace in a deployment pipeline.

Solution

Luckily the solution is very simple! 

• Don't use the Initial Catalog option in combination with SSMS, leave it at <default>
• Or, if for any reason you need the above option selected, install SSMS 19 Preview 4
• This preview version is a side-by-side installation, so it installs next to SSMS 18.x

I hope this helped you if you encountered the same problem.

A No-Code Method to Refresh One Table From a Power BI Dataset in the Service

Context

A few weeks back I was working on a dataset at a client where I needed to import Excel files from a folder into said dataset. I filtered the files on a prefix and loaded around 30 files of the same structure to a table in my dataset. The Excel files are exports from a budgetting system (I know, right?) that have to be updated multiple times in the next coming weeks on an ad-hoc basis.

After the Excel files are updated I currently have 2 choices:

• Open the pbix-file and refresh the specific table that loads the files, and then publish to the service. This however again triggers a refresh in the service after publishing. Depending on the connection I have in the pbix (subset of rows from dev/test/prod) I might have to wait for the refresh in the service anyhow
• Refresh the dataset in the service and wait for that to finish

And it's not that the dataset is thát big, but of course waiting (for 20 to 30 minutes) for a refresh would be a waste of time. And it doesn't really matter how long it exactly takes, if you're waiting for something, it always takes too long, right?

Solution

But as you might have noticed from the title of this blog, there is also another solution 😀.
Spoiler alert: you do need a Premium license.

Marc Lelijveld previously talked about the automation of triggering a single table to refresh in the Power BI Service, with PowerShell and a TMSL script. 

But what if you're not (that) familiar with PowerShell and / or TMSL? And maybe it's not going to be part of an automated schedule, but you just want to be able to execute it ad-hoc, when necessary?

Luckily there's the XMLA endpoint to the rescue. You can connect to any Premium (Capacity or Per User) workspace via the XMLA endpoint with SQL Server Management Studio (SSMS) to do a (single) table refresh.

There's a few things you'll have to consider before being able to do this..

• Enable XMLA read-write
• Get the XMLA endpoint connection string
• Connect via SSMS
• Refresh your table(s)
• Check the outcome of the refresh in SSMS
• Or alternatively check the refresh history in the service

Let's look at the individual steps in more detail.

Enable XMLA read-write

The first thing you need to do is to enable the option Read Write on the XMLA Endpoint of your Premium capacity.

This setting is available in the Admin Portal, either under Capacity settings or Premium Per User, depending on your license.

XMLA Endpoint connection

You can get the connection URL from the workspace Settings page, under the Premium tab.

More info on the documentation page.

Note: Connecting to a My Workspace by using the XMLA endpoint is currently not supported.

Connect via SSMS

Use SQL Server Management Studio to connect to the URL obtained in the previous step. Just be aware that you need version 18.9 or higher to do so.

Make sure you use the following option for Authentication:

• Azure Active Directory - Universal with MFA

Next to connecting to and looking at properties of your Power BI models, this method also supports executing DAX, MDX, and XMLA queries.

SSMS isn't the only tool supported by the XMLA endpoint, you can pick any of the tools mentioned here, e.g. Excel, SQL Server Profiler, DAX Studio or Tabular Editor to name a few of them.

With some tools it might be necessary to also provide the Initial Catalog (the dataset to connect to in your workspace). The datasets in your workspace will eventually show as databases under your AS-server:

UPDATE December 19th 2022:

When using SSMS and the option to use an Initial Catalog, you (might) run into an error, read my update post how to avoid this.

Refresh your table(s)

Now onto the actual refreshing of my tables. 

• Right-click the table you want to refresh and select Process Table

• Select the right processing option depending on your needs, I used a full refresh
• Optionally select other tables to refresh
• Click OK and wait for the refresh to complete.

Next to refreshing your table(s) in SSMS, you could also script out the refresh command and use it to automate the process. Because I only need to refresh it on an ad-hoc basis I'm good with my solution for now.

Refresh history

This type of refresh shows as a Via XMLA Endpoint in the Refresh History of your dataset properties in the service.

In any case you ever want to cancel a running refresh, also with Premium and the XMLA endpoint set to Read/Write, have a look at this post how to Cancel a refresh with a SessionID (instead of SPID) and DAX Studio.

Conclusion

In this post I provided a UI-only solution to refreshing a single table in your Power BI dataset. Hopefully this post gave you some insights.
Have you already used this method before?
Do you use it often?
Do you use other methods to refresh a table in a dataset?

I'd love it when you provide more details in the comments!