Forum Discussion
SSMS (400) Bad Request error while refreshing partition on premium capacity dataset
Hello!
I've seen some posts regarding this error but I think that this is another behaviour.
I have a dataset with a large fact table, specs:
- 1 billion rows aprox.
- No transformations in power query.
- No calculated columns.
- Not many columns on fact table.
- Incremental refresh ( 6 years of history, refresh the last 2 days).
- Stored in Premium capacity (configuration for XMLA seems fine).
I'm using SSMS in order to refresh individual partitions instead of all at the same time, the problem in that sometimes I could fulfil this, and another times i get this error:
As I said, sometimes it just works fine, like this:
The warning says something like "The expression refers to several columns. Multiple columns cannot be converted to a scalar value".
The gateway seems to be undersized, could this be the only cause to this error or I'm missing something else?
This is the version that I currently have in SSMS.
Thank you!
HI pacoduabe,
I'd like to suggest you take a look at the following link that mention the similar issues if it helps with your scenario:
Solved: SSMS (400) Bad Request error attempting connect to... - Microsoft Power BI Community
Regards,
Xiaoxin Sheng
3 Replies
HI pacoduabe,
I'd like to suggest you take a look at the following link that mention the similar issues if it helps with your scenario:
Solved: SSMS (400) Bad Request error attempting connect to... - Microsoft Power BI Community
Regards,
Xiaoxin Sheng
Hello Anonymous! I took a look into the post, the error is similar but it seems that they didn't cannot connect via analysis services at all while my error pops out while executing a query.
I will ask to update SSMS version and drivers as mentioned in the post (since is a VM in which I have not admin access) and try again, in any case, I do think that the gateway is still undersized.
Thank you!
Good news! Or bad news, I don't know for sure. I've been able to make a full refresh on Power BI service and I still get the same issue on SSMS. Since it's a VM and I haven't admin privileges I cannot update the SSMS or its drivers. In any case, since the full refresh worked in PBI service, this behaviour must be caused by an outdated version or there are some issues with the premium capacity settings that must be changed.
