March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi,
I'm looking for some suggestions with the logic on below thought-
In the case of import mode, I usually use one PBI file to create the model, publish it and then use it as a live/import connection for other related reports.
Is it wise to follow the same practice if I have a model built on using only direct queries due to high data volume?
I mean create a model using a Direct query publish it and then use is a live connection for the rest of the related reports (2-4 report using that data set)
Thank you for looking into this.
Hi @amitchandak ,
Yes, I agree that we can do it. I'm seeking some suggestions from a Performance viewpoint.
In a normal case, if I have a file with a direct query, it will hit to data source let’s say SQL every time a user does any interaction on the report.
But in case using a single model file created with a direct query and using it as a source for a few other reports will make all those queries go through one single PBI report.
furthermore first main model file will extract data from SQL then it will pass along that data to other connected reports that will consume time.
Also if there are 100 + users using all those related reports and all backed quires going through a single file which seems to be challenging from the viewpoint of limitation on max 20 queries can be executed a single point of time. The rest of the queries will be queued which will reduce the performance.
@Gyan , You can create a direct query dataset and you use that as live dataset in new report
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
User | Count |
---|---|
90 | |
89 | |
85 | |
73 | |
49 |
User | Count |
---|---|
169 | |
144 | |
90 | |
70 | |
58 |