Query based collections in the SQL 2005 based application fail.

The SQL2005 application in Longitude collects data using both WMI and SQL Queries running over a JDBC connection. The following collections are made using JDBC:

• FailedJobs
• FrequentQueries
• Index
• LongestJobs
• WorstQueries

If the JDBC based collections are failing, try the following debug steps:

1. If the error message you receive includes a "Connection timed out" message, try restarting the Statistics Server, and then register the SQL2005 application again for the instance you would like to monitor.
2. If all the SQL Query collections are failing, verify that you can connect to the SQL Server using a SQL Query transaction. The SQLQuery transaction will first check that it can connect to the specified server using a SQLConnect transaction and then run a query over that connection. If this fails, check the configuration information used for running the query. The following properties can be modified for the JDBC connection:
   
   DatabaseInstance - The default setting is blank for the default database instance.
   
   Port - The default port for the connection is 1433 - please verify that your SQL instance has not been configured to use a different port.
   
   DatabaseUser and DatabasePassword - By default the query tries to run using Windows Authentication based on the permissions of the Statistics Server Service account. You can specify a username and password if you need to use SQL based authentication.
3. If step #1 and #2 have not resolved the problem, try running the query that Longitude is using directly against the database. Please post a reply to this topic with the details of the failing collector (or collectors), and we'll post an update with the query to try.