>When you create and deploy a dashboard, by default PBI creates an in-memory compressed dataset. So users are interacting with the in-memory dataset, not with the data in SQL Server. You can define refreshes for the data, which would point back to SQL Server (possibly through a data gateway)
>
>You "can" set up what's called DirectQuery.....where the dashboard queries back to the sql server (or other data source) every time. However, that's not "normally" the usage pattern. More often than now, users interact with a PBI data model (for best performance), with the idea that data will be refreshed on some periodic schedule.

Thanks, I understand the general line of BI is with read only data for analysis and decision making process. There will always be a time, however, that someone will ask for something to be updated. Generally, a process prepares the data into the platform. There would be pivot tables. If someone would like to add a status for example, I guess the best is to update the status from the source application itself. But, let's assume the soure application does not have it but the ETL phase does require it. I guess it would just be a matter of dealing with read only data from that point.

As for IIS, I understand Power BI has some web publishing built-in tools which allow the possibility to negotiate with the web without a web server. I see also it supports the publishing through the generation of iframe HTML code which allows us to insert that code into a web page. When you built that fancy demo, is this the technique you used?