Data Source Options can be access by clicking the expand button
on the Data section of the main menu on the Data Discovery tab:
Data Sources can be managed using the Data Source Manager.
Timeouts
The time (in seconds) to wait for a connection to the database server. The default value is 15 seconds.
This setting should only be changed if you know you are running on a slow network and it takes longer to make a data connection to your database server than normal.
The wait time (in seconds) before terminating the attempt to execute a query sent to your database server before generating an error.
This setting should only be changed if queries sent to your database server take a very long time to run.
DSF uses this setting for 2 purposes:
1) When running the preview sample of selected data elements.
DSF only queries a small number of records as a sample so it should be a quick process. As such, no change to this option should be needed.
If you are still experiencing a "Command Timeout" error, there could be a query that is taking a long time to execute. This may be due to the source of an original data element being derived from a long running Subquery or query that includes an aggregate function.
An overloaded or under sized database server may also cause this error to occur. Increasing this value may remove the timeout error but we do not recommend doing so. The correct solution would be to investigate why the original discovery query is taking too long to run in the first place.
2) When the Test Database Views Before Discovery option is enabled (Option can be found in Discover Options on the Data Discovery tab).
Enabling this option requires that DSF execute any database Views that it finds during discovery to ensure they are valid before learning from them. When this happens, DSF is at the mercy of the original query designer. If the original query was constructed badly, it's possible a timeout error can occur when DSF trys to execute it. This may not always be the case, but is possible.
To reduce this possibility, DSF will attempt to run the query returning only 1 record in the resultset. However, some database queries can still be slow due to missing indices or any other number of reasons beyond our control.
If your are experiencing a "Command Timeout" error, you can increase the timeout value, exclude the View or disable the Test Views option.