Forum Discussion
SQL 2016 on Power BI Gateway server
Anonymous It largely comes down to resource usage. If the gateway will only ever refresh at night, then you likely have minimal to no impact. But, if you know you will scale, and more reports will start to require refresh then depending on what the SQL server is doing there might be some contention, delays or failures. The recommendation for a seperate gateway machine is so that as you scale up and add more and more reports that require more resources to refresh that you won't impact your reports. Outside of that, there is no issue. I've had both scenarios work well (dedicated machine vs. shared)
Anonymous It largely comes down to resource usage. If the gateway will only ever refresh at night, then you likely have minimal to no impact. But, if you know you will scale, and more reports will start to require refresh then depending on what the SQL server is doing there might be some contention, delays or failures. The recommendation for a seperate gateway machine is so that as you scale up and add more and more reports that require more resources to refresh that you won't impact your reports. Outside of that, there is no issue. I've had both scenarios work well (dedicated machine vs. shared)
Thanks you for your clear answer! This helps me a lot.