Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have a site where we are planning a multi-node Qlik Sense architecture. This will consist of one centre/reload node and one consumer node.
We are considering installing the central/reload node on the data warehouse server. This means that Qlik Sense and SQL Server will reside on the same machine. This server only exists for the data warehouse, so we can schedule jobs such that Sense reloads commence after the SQL Server jobs complete.
We expect it will also give us quicker reload times as we have found network congestion sometimes slows down data transfer from SQL Server to other machines. (we are already running QlikView and find reloads on the SQL Server machine take half the time of reloads from other machines). To be clear, we will not install Sense on the same server as QlikView.
We are aware that there could be resource constraints (CPU and RAM) if SQL and Sense are running jobs at the same time, but we should be able to minimise that.
Are there likely to be any other problems with this set up? Port conflicts or any other?
Thanks for your help.
Hey Michael,
Outside of resource contention with two products which use non-trivial CPU as well as RAM, the only obvious one would be port contention. MS SQL Reporting Services does bind to 443 if I recall, so those that aspect of MS SQL + Qlik Sense would not co-exist. Otherwise, it should be fine.
Hey Michael,
Outside of resource contention with two products which use non-trivial CPU as well as RAM, the only obvious one would be port contention. MS SQL Reporting Services does bind to 443 if I recall, so those that aspect of MS SQL + Qlik Sense would not co-exist. Otherwise, it should be fine.
Thanks.
We are not using SSRS on that server, so it should be fine.