Forum Discussion

HB2023's avatar
HB2023
Regular Visitor
3 years ago

Deploying Tabular model to Premium Capacity

Hi,

 

We're currently moving all our tabular models to Premium Capacity manually.

This means importing the models from AAS using Visual Studio and then deploying to a Permium workspace.

As we have less than a dozen models this is manageable and has worked on a handful of models.

 

However, on a few of the models I get the following error when deploying:

 

Failed to save modifications to the server. Error returned: 'M Engine error: 'Microsoft.Data.Mashup.Preview; <ccon>This document contains a duplicate member 'Date'.</ccon>'.

Technical Details:
RootActivityId: 1bfb8d3f-e40f-4728-acb5-1b9b5298c8b4

 

I can safely say that we do not have duplicate date key values but I still do not understand what this relates to and how to correct the issue?

 

Any guidance and help would be appreciated.

 

Thanks. 

 

Need Help

4 Replies

  • HB2023's avatar
    HB2023
    Regular Visitor
    3 years ago

    Hi GilbertQ,

    Thanks for replying.

    I have tried migrating through Azure Analysis Services to Power BI Premium tool but you either get success or failure and still a very limited description of the failure – see screenshots below.

    So, going back to my initial post, I would like to understand what that message means?
    Otherwise, any ideas on what the migration error means and why is it happening?

    Thanks

     

     

     

  • GilbertQ's avatar
    GilbertQ
    Super User
    3 years ago

    Hi HB2023 

     

    I am not sure why that would happen and what you might be able to do is to connect SQL Profiler and then see when the restore is happening why it fails?

    • HB2023's avatar
      HB2023
      Regular Visitor
      3 years ago

      Hi GilbertQ ,

       

      Apologies for not getting back to you ealier on.

      I did eventually find out what the issue was, not through using SQL Profiler, but digging deep into the model.

       

      We have some tabular models which were created way back when at 1200 compatability level.

       

      Just by changing/upgrading the compatability level from 1200 to 1500 on the model will still give you the same error message. When creating models at an earlier compatibility level it created expressions with the same name as the partitions.

       

      The only way around this issue was in recreating the models from scratch at 1500 compatability level, the minimum requirement when migrating to Premium.

      This meant we didn't have to deal with any unforeseen legacy issues.

       

      We have now recreated and migrated our old models onto a Premium Capacity workspace and they are working fine.

      The only downside with Premium Capacity is that you can only schedule up to 48 refreshes per day.

      The expectation was to have our models refresh every 5 minutes, and with the aid of Azure runbooks we have been able to achive this.

       

      Thanks