Forum Discussion
SQL Server and Gateway on same Server
Hello everyone,
we are in the progress of migrating our reporting from an OData datasource to a SQL server datasource as we've seen massive performance improvements when refreshing datasets stored on a SQL server.
Originally we were planning to use an Azure SQL Server but we're running into more and more problems and are now considering hosting the Server ourselves. This would of course mean that we also need a gateway to allow refreshes on the PBI service.
Is there any reason why one should not install the gateway on the same machine as the SQL Server other than security/privacy concerns? Can the gateway access a the SQL Server hosted on the same machine?
The obvious upside is of course that the gateway wouldn't have to go through the network to get data from the SQL server, thereby decreasing latency and ultimately increasing throughput.
Thanks!
- Hi there
I have had my gateways installed on SQL Servers for quite a while with no issues and it works really well
Just make sure that there is enough CPU & Memory for when your dataset refreshes to ensure that it will not consume too much and slow down your SQL Server. That would be the only things to look out for.
5 Replies
- Hi there
I have had my gateways installed on SQL Servers for quite a while with no issues and it works really well
Just make sure that there is enough CPU & Memory for when your dataset refreshes to ensure that it will not consume too much and slow down your SQL Server. That would be the only things to look out for. Just a little followup:
We have this setup running for about a month now and its working perfectly.
My only concern is memory usage as the gateway does seem to like its RAM. I've limited the SQL server to 45GB memory on a 64gb server to leave some space for the gateway and OS to expand into.
