If I have NitroAccelerator installed on a client or server, will I still be able to connect to a client/server that does not have NitroAccelerator installed?
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.
Is NitroAccelerator cluster aware?
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.
Does NitroAccelerator work with protocol encryption enabled within SQL Server?
Unfortunately, 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.
If access to the database is through an application server, do the PCs accessing that application server need NitroAccelerator installed as well?
No. NitroAccelerator will only compress the data transferred between the application server and SQL Server, so it will not need to be installed on the individual PCs accessing the application server.
Will NitroAccelerator run on a virtual server?
Yes, NitroAccelerator can be run on a virtual machine.
What is the CPU overhead when using NitroAccelerator?
This will depend on the compressibility of your data, but we typically see overhead in the range of 1-3%.
Will NitroAccelerator speed up my backups?
No, NitroAccelerator only compresses the TDS protocol, and so will not impact backup speed.
How does NitroAccelerator handle uncompressible data?
NitroAccelerator uses intelligent compression to detect and bypass uncompressible data. The default threshold below which NitroAccelerator will stop compressing is 20%, but this can be configured per server. Once the compressibility again rises above the threshold, NitroAccelerator will resume compressing the data stream.