How to Target Microsoft SQL Servers in Turbonomic

Document created by rstrehlke Expert on Jun 9, 2015Last modified by vasile on Nov 28, 2016
Version 7Show Document
  • View in full screen mode

***The following setup is only applicable to users with the Application Control Module or Application Edition***


(This applies for the versions older that 5.4; for "How To Target SQL Servers in Turbonomic  (5.4 and later)" see


In this document we’ll review how to target Microsoft SQL Servers within your Turbonomic instance.


Turbonomic 5.2 supports Microsoft SQL Server 2008 R2, 2012, and 2014. As of now, each SQL server instance must be targeted individually. In the Admin panel, the SQL Server information should be filled out as follows:


Once the configuration is complete, select “Save” and “Rediscover"



Port number 1433 is the out of the box default SQL Server Port.


“Service” specifies the name of an individual database instance on that SQL server, not a service itself.


“Username” must be a present login within the Security folder in the SQL Server Object Explorer (LDAP authentication is coming). If creating a new SQL Login, make sure to select the SQL Server authentication and uncheck “Enforce password policy”:



This user should also have permissions to connect to the database through SQL:



As well as read the server state:


If you are unable to connect with the above configuration, check the following.


These services should be started and not set to disabled:



Make sure TCP/IP is enabled in SQL Server Configuration Manager, and that the port is what you specified in the admin panel configuration:



You will eventually be able to see your targeted SQL database servers discovered in the Inventory tab:



From here, you will be able to see decisions based on the demand of the application from the virtual machine. Metrics collected include:

- DBMemory

- Connection

- Transaction

- ResponseTime

- TransactionLog

1 person found this helpful