The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
How long it will take approximately to process 10K records on Power BI Report Server (on-premises) using import mode on SQL Server Database and how much is the maximum number of records Power BI Report Server can handle ? I am using P1 capacity?
Solved! Go to Solution.
Hi @powerbiexpert22 ,
When using Power BI Report Server (on-premises) in import mode with a SQL Server database under P1 capacity, the time it takes to process 10,000 records can vary based on several factors, including query complexity, data model optimization, network latency, and server specs.
However, generally speaking, 10K records is a relatively small dataset, and processing (refresh/loading) it should take only a few seconds to a couple of minutes at most on a well-optimized model. In terms of capacity, while there is no hard-coded record limit, P1 capacity is designed to handle datasets up to 25 GB per dataset (post-compression) and supports substantial workloads.
That said, performance and reliability will depend heavily on model design, data transformations, and concurrent usage. For best results, it’s important to follow best practices in data modeling and monitor memory consumption during peak loads.
Hi @powerbiexpert22 ,
You can refer this document here which talks about Capacities and SKUs.
What is Power BI Premium?
Additionally, you can follow the discussion on Premium P1 capacity on community forum here:
https://community.fabric.microsoft.com/t5/Service/Premium-P1-Capacity/td-p/3439637
Hope this helps!
If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
Hi @powerbiexpert22 ,
Just wanted to check if you had the opportunity to review the information provided?
If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank You
Hi @powerbiexpert22 ,
Just wanted to check if you had the opportunity to review the information provided?
If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank You
Hi @powerbiexpert22 ,
Just wanted to check if you had the opportunity to review the information provided?
If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank You
Hi @powerbiexpert22 ,
You can refer this document here which talks about Capacities and SKUs.
What is Power BI Premium?
Additionally, you can follow the discussion on Premium P1 capacity on community forum here:
https://community.fabric.microsoft.com/t5/Service/Premium-P1-Capacity/td-p/3439637
Hope this helps!
If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
Hi @rohit1991 ,
can you share the documentation which states 25 GB per dataset for P1 capacity?
Hi @powerbiexpert22 ,
When using Power BI Report Server (on-premises) in import mode with a SQL Server database under P1 capacity, the time it takes to process 10,000 records can vary based on several factors, including query complexity, data model optimization, network latency, and server specs.
However, generally speaking, 10K records is a relatively small dataset, and processing (refresh/loading) it should take only a few seconds to a couple of minutes at most on a well-optimized model. In terms of capacity, while there is no hard-coded record limit, P1 capacity is designed to handle datasets up to 25 GB per dataset (post-compression) and supports substantial workloads.
That said, performance and reliability will depend heavily on model design, data transformations, and concurrent usage. For best results, it’s important to follow best practices in data modeling and monitor memory consumption during peak loads.
User | Count |
---|---|
82 | |
82 | |
35 | |
32 | |
32 |
User | Count |
---|---|
93 | |
79 | |
62 | |
54 | |
51 |