Forum Discussion

DenisVarshavsky's avatar
DenisVarshavsky
Frequent Visitor
2 years ago
Solved

Importing tables from MariaDB - Error: user exceeded max user connections

Hi,

Would appreciate any insight regarding the following error message: [ma-3.1.20]user has exceeded the 'max_user_connections'


BACKGROUND INFO:
I am attempting to import a large number of tables to Power BI from a database managed using MariaDB management system.

STEPS:
These were the steps I followed:

  1. Installed ODBC connector driver for MS Windows 64-bit OS: https://mariadb.com/downloads/connectors/connectors-data-access/odbc-connector/
  2. Created data source in Power BI:
            - Selected 'MariaDB'.
            - Inserted data source details (server, port, database name) and selected 'Import' connectivity mode.
            - Selected the relevant tables from the list and proceeded to Loading them.
  3. At this point I receive an error message: 
           - [ma-3.1.20]user '---' has exceeded the 'max_user_connections' resource (current value: 5)

                - Model View shows first four tables, while for the rest of the tables the abovementioned error message appears (see screenshot below)

It appears that for each imported table Power BI allocates one connection. Given that my user has a limit of 5 connections: one is being used to connect to the database and then four remaining connections appear to be used to load four tables only.

I thought that increasing max connections number for my user would be an acceptable solution, but our DBA is concerned this will put lots of stress on the database. 

Would appreciate any ideas on how to resolve the issue.

 

 

 

 

 

  • Thanks for the suggestion.
    I found a workaround by disabling parallel loading in the Options. This forces Power BI to load tables sequentially (while previously these were treated as multiple concurrent jobs). 

2 Replies

  • Use dataflows for individual tables or groups of tables.. Then in Power BI connect to the dataflows.

  • Thanks for the suggestion.
    I found a workaround by disabling parallel loading in the Options. This forces Power BI to load tables sequentially (while previously these were treated as multiple concurrent jobs).