Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

PBIX Size problems vs embedded premium capacity

 

I have a PBIX size of 1,048,000 KB.    I had difficluty publishing the PBIX to a premium capacity backed workspace on A1 tier and had to scale up to  A2 (limit 5 GB RAM).     Here is the error in both instances:

 

 

I was a ble to reduce the file size to 783,127KB and succeeded in publishing to  Service.    

With Dataset unchanged,  when I try to refresh same PBIX in service, I get the following error:

 

Questions:

  1. How is it I am unable to refresh this size of PBIX of 788,000K despite that we are on A2 (5 GB RAM)
  2. What is the limit of PBIX that can be resfreshed with this premium capacity? 

 

Need Help
  • v-lionel-msft's avatar
    v-lionel-msft
    5 years ago

    Hi Anonymous ,

     

    1. The possible reason is that your dataset will exceed 1GB after refreshing, so the dataet refresh failed.

    2. For A1, there is indeed a 1GB limitation.

    Datasets in Import mode 

     

    Best regards,
    Lionel Chen

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

     

4 Replies

  • v-lionel-msft's avatar
    v-lionel-msft
    Community Support
    5 years ago

    Hi Anonymous ,

     

    Size considerations 

    Please refer to the documentation above.

    Although you can upload successfully, the data set size will exceed 1GB after you refresh, so the refresh fails.
    In other words, A2 only supports .pbix files up to 1GB.

     

    Best regards,
    Lionel Chen

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

     

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    v-lionel-msft  

     

    Thank you for your response.  Just an FYI:

     

    1. My PBIX file size is still 780,000KB, It is has not grown to 1GB, yet Refresh is failing. 

    2. Are you confirming that A2 premium capacity can only accomoddate PBIX up to 1GB even though documentationb is for up to 5GM RAM?   

     

     

     

     

    • v-lionel-msft's avatar
      v-lionel-msft
      Community Support
      5 years ago

      Hi Anonymous ,

       

      1. The possible reason is that your dataset will exceed 1GB after refreshing, so the dataet refresh failed.

      2. For A1, there is indeed a 1GB limitation.

      Datasets in Import mode 

       

      Best regards,
      Lionel Chen

      If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

       

  • Eugene_Ov's avatar
    Eugene_Ov
    Helper I
    5 years ago

    Anonymous I managed to deal with this using XMLA read-write, in two steps:

    Process database -> Process Clear

    Process database -> Process Full

     

    This method has some disadvantages: during this process, you'll have dataset with no data. I also experienced some connectivity issues when Full processing ended with timeout error. 

     

    Additionally, you could try another solution: automate SKU tier raising before processing the cube and downgrading after it's finished.

     

    Eugene