Forum Discussion
Gateway Best Practices
- 2 years ago
- at least two cluster members (more is better). Make sure that they have exactly the same configuration. All the drivers, all the ODBC settings, all the TNS entries etc.
- lots of cores and fast NIC (for Direct Query workloads)
- lots of memory and disk space (for Import Mode workloads)
- do not install anything else on the gateway VMs
- move the report and spooler folders to a different spindle.
- wait before installing a newly released gateway version. There is no undo button. You will have to uninstall, reinstall and reconfigure if you mess up
- never ever lose the recovery key. DO NOT lose the recovery key
- make friends with the network people. Without a functioning and fast proxy your gateway VMs are nothing more than electronic door stops.
- implement your own telemetry monitoring. The default gateway monitoring template is usel... uhm has room for improvement.
- at least two cluster members (more is better). Make sure that they have exactly the same configuration. All the drivers, all the ODBC settings, all the TNS entries etc.
- lots of cores and fast NIC (for Direct Query workloads)
- lots of memory and disk space (for Import Mode workloads)
- do not install anything else on the gateway VMs
- move the report and spooler folders to a different spindle.
- wait before installing a newly released gateway version. There is no undo button. You will have to uninstall, reinstall and reconfigure if you mess up
- never ever lose the recovery key. DO NOT lose the recovery key
- make friends with the network people. Without a functioning and fast proxy your gateway VMs are nothing more than electronic door stops.
- implement your own telemetry monitoring. The default gateway monitoring template is usel... uhm has room for improvement.