Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago
Solved

PowerBI Dataset Creation Error

Hello,

I'm running into a very odd error while creating Datasets for Power BI using Microsoft.AnalysisServices.  Basically I'm attempting to clone a dataset from an existing one by using Microsoft.AnalysisServices.Tabular's CopyTo() method to copy the Model from one dataset into another.  This has been working fine for us on our P2 instance that we setup but lately everything has stopped working and now throws the following exception:

Failed to save modifications to the server. Error returned: 'The request failed due to throttling, because the number of datasources exceeded the maximum limit.

Technical Details:
RootActivityId: 53363332-39fb-411e-ad6d-f38c88f5107d
Date (UTC): 7/30/2024 11:05:48 PM
'.

Furthermore, I'm seeing similar messages when I attempt to look at these datasets in SSMS:


Would anyone happen to know what limit I'm running into here?

Thanks,

Need Help
  • Anonymous's avatar
    Anonymous
    2 years ago

    I ended up opening a ticket with Microsoft on this one and found the root of the issue.

    We were using a Service Principal to access the Power BI API but it turns out there are some hard limits on what a single account can do.  In this case there's a limit of 1,000 Datasources that an account can create which we quickly hit with our process.  The only way around this is to create even more Service Principals to handle further requests with Power BI.

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi Anonymous ,

    Is the amount of data in your dataset growing every day? Regarding your error message, it may be that the number of rows in the dataset exceeds the row limit of 'CopyTo'. You can try to reduce the amount of data in the dataset and try again.

     

    Best Regards,
    Wenbin Zhou

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    I ended up opening a ticket with Microsoft on this one and found the root of the issue.

    We were using a Service Principal to access the Power BI API but it turns out there are some hard limits on what a single account can do.  In this case there's a limit of 1,000 Datasources that an account can create which we quickly hit with our process.  The only way around this is to create even more Service Principals to handle further requests with Power BI.