If you are not seeing any compression statistics in the SQL Boost Control Console, ensure the following:

• SQL Boost was installed under an administrator account.
• Your SQL Server service was restarted after installation.
• You are connecting using the TCP/IP protocol. You may need to create an alias to do this, or simply disable the other protocols.
• If connecting locally, make sure that the shared memory protocol is disabled.
• If connecting from a client that was installed under terminal services, make sure the Installing Under Terminal Services section was followed.
• If you have reinstalled SQL Boost, that the machine has been rebooted.
• If you have restarted the SQL Boost Watch service, that your SQL client has been re-launched.
• All client applications that send traffic to SQL Server were re-launched. Please note that during testing, any time SQL Boost is started or stopped (via the SQL Boost Control Console or by starting/stopping the SQL Boost Watch service), your client applications must be closed and then re-launched.

SQL Boost also includes a diagnostic tool, which may be helpful in troubleshooting. You can access this tool via the help menu in the SQL Boost Control Console. This diagnostic output includes:

• Which SQL Servers are detected by SQL Boost and the protocols that are enabled for each.
• Whether SQL Boost’s client-side functionality is currently enabled on the system, which usually indicates whether the SQL Boost Watch service is started or stopped.

Need more help? Search the IDERA Customer Support Portal