August 29, 2015 at 8:04 am
Using SQL 2012 Enterprise on Windows Server 2012 R2 Data Center O/S (w/ 512 GB RAM)
- We're using 3rd party software called "Composite" which mandates the creation of ODBC connection to connect to it's data sources. (we have both 32-bit and 64-bt ODBC "SYSTEM DSN" connections predefined on our SQL Server)
PROBLEM: Receiving SSIS pkg: ODBC Connection Timeout - ERROR [HY000] The request timed out after '15' seconds.
QUES:
- Is there a REGISTRY SETTING we can change to bump up the default ODBC timeout from 15 secs?
- We've tried adjusting a few TIMEOUT parms listed below. HOW can we increase the ODBC timeout to 60 seconds?
BACKGROUND:
- We've set the ODBC Connection SYSTEM DSN "Connection Pooling" tab Pool timeout property to 90
- We've set our SSIS, Data Flow, DESTINATION 'CommandTimeout' property to 100 (and also tried setting to 0 which is supposedly unlimited)
- In our 'Connection Manager' Connection properties, we don't see a timeout parameter to set
- Is there a REGISTRY SETTING we can change to bump up the default ODBC timeout from 15 secs?
January 12, 2016 at 3:32 am
The timeout settings are a server side property so they must be set on the server as you establish a connection but only if the ODBC driver allows you to set them. Open the ODBC connection and go to the advanced settings if it exists and set it there - if properties can be set you will have a property and a value. Hopefully that gets you on the right path.
January 12, 2016 at 6:43 am
In the Data Flow task have a look at the properties of the ODBC Source Task. You should see a property for Statement Timeout. It is Zero by default but you could try tweaking it.
January 12, 2016 at 6:46 am
Note post was several months old ...
I would recommend contacting the vendor if you can't get it sorted. y fiahing through theor documentation or doing trial and error testing with your configuration.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply