Troubleshooting
If you are not seeing compression statistics in the NitroAccelerator Console, please ensure the following:
NitroAccelerator is installed under an administrator account.
Firewall settings whitelist the required ports.
That all connected systems are using the updated version of NitroAccelerator.
All client applications that send traffic to SQL Server have been re-launched.
Please note that during testing, any time NitroAccelerator has been started or stopped (via the NitroAccelerator Control Console or by starting/stopping the NitroAccelerator Watch service), your client applications must be closed and then re-launched to establish new connections.
You are connecting through the TCP/IP protocol.
The ports in use are whitelisted within your firewall settings.
This is required in order to benefit from NitroAccelerator. If your system default is another protocol, you can create an alias that uses TCP/IP, and connect to the SQL Server using this alias.
Yes. NitroAccelerator does not affect any connections with non-NitroAccelerator clients or servers. However, you will only get the compression benefit on connections that have NitroAccelerator installed on both ends.
This will depend on the compressibility of your data, but we typically see overhead in the range of 1-3%.
Yes, NitroAccelerator can be run on a virtual machine.
NitroAccelerator does not work with SQL Server protocol encryption enabled. Encrypted data does not compress well, so NitroAccelerator will just bypass and not compress any encrypted packets it encounters. Because of this you will not see any benefit with NitroAccelerator until the protocol encryption is turned off. However, NitroAccelerator includes its own option for protocol encryption, which is done after the data is already compressed. This maintains the performance benefit while still securing your connection.
Encryption is required if your connections is going over the internet. Otherwise, it is optional. NitroAccelerator includes encryption tuning settings within the console and all caching operates within existing ports and local kernels. Th Nitro team takes security very seriously. Visit Security Overview for more info.
Yes. To run NitroAccelerator on a cluster, simply install the product on each node. On failover, your clients will continue to benefit from a compressed connection.
Multiple Active Result Sets (MARS) is a separate protocol on top of the Tabular Data Stream that is extremely chatty and tends to perform very poorly over slow networks. To maximize performance, we recommend that our customers not use MARS, but instead use a different connection for each query. NitroAccelerator will provide a much greater performance benefit on connections that do not have MARS enabled.
Request your Free Trial to receive your download files and documentation.
Not ready to trial yet? Book a Free Demo Consultation.