Setting Max Parallelism on Refresh #269
Unanswered
EthanEverett
asked this question in
🙋♀️TE3 Q&A
Replies: 2 comments
|
alwortman answered: Configurable on a per-datasource basis via "Max Connections" property. That is the easiest way to prevent these kinds of errors. I would be curious how TE3 generates the XMLA sequence command when refreshing multiple tables at once...maybe there is something there? |
0 replies
|
I guess you could monitor the model using sql server profiler or Azure Log Analytics, to capture the refresh commands? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
For some models the data sources get overwhelmed due to the number of concurrent requests and will time out. We are able to control for this by deploying to SSAS and then specifying Max Parallelism when refreshing in SSMS via the code below:
{
"sequence": {
"maxParallelism": 5,
"operations": [
{
"refresh": {
"type": "full",
"objects": [
{
"database": "TabularModel"
}
]
}
}
]
}
}
Is this the same as the Max Connections setting? Or is there a setting available for specifying Max Parallelism in TE? If so, any help is much appreciated.
All reactions