Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

ODBC - Problem: too long execution time of ADODBConnection

Created by: ZHK at: 7/26/2017 8:33 AM (2 Replies)

Rating (1)

Thanks 1

3 Entries

7/26/2017 8:33 AM	Rate (0)
ZHK Bronze Member Joined: 2/18/2013 Last visit: 1/13/2025 Posts: 142 Rating: (12)	Well, after about ten years I have faced with the same problem: too long execution time of ADODBConnection.Open if network is down. If there is a remedy - let us know please. P.S.: this code below does not affect it anyway, script freezes about 43 seconds. conn.ConnectionTimeout = 5 conn.CommandTimeout = 5 ------------------------------------------------------------------------------------------ Split from Connect remote SQL server, set ODBC timeout?.
	Last edited by: Jen_Moderator at: 7/27/2017 11:31:20 AM New subject after splitting
Suggestion To thank Quote Answer

7/26/2017 3:25 PM	Rate (1)
Michael K Gold Expert Joined: 9/3/2008 Last visit: 1/13/2025 Posts: 932 Rating: (163)	Hi ZHK, I suspect the problem is not really with the odbc command. The problem is with the TCP/IP communication that is being used to send the command over the network. Because the computer does not respond, the TCP/IP has a timeout of about 30 second or so. To improve your code, you would need a kind of ping or check before calling the odbc command to check if the SQL server is available on the network. But you will always have the danger of network disconnection and scripting pausing.
	Last edited by: Michael K at: 7/26/2017 3:25:45 PM Michael
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users ZHK

7/27/2017 7:59 AM	Rate (0)
ZHK Bronze Member Joined: 2/18/2013 Last visit: 1/13/2025 Posts: 142 Rating: (12)	Thank you, Michael K it is a good workaround. Though script is still freezing waiting for ping, but much less (about 3-4 sec). I used this code to ping my server: Function Ping(ByVal myHostName) ' This Function returns True If the specified host could be pinged. ' myHostName can be a computer name or IP address. ' The Win32_PingStatus class used in this function requires Windows XP or later. ' This function is based on the TestPing function in a sample script by Don Jones ' http://www.scriptinganswers.com/vault/computer%20management/default.asp#activedirectoryquickworkstationinventorytxt ' Standard housekeeping Dim colPingResults, objPingResult, strQuery ' Define the WMI query strQuery = "SELECT * FROM Win32_PingStatus WHERE Address = '" & myHostName & "'" ' Run the WMI query Set colPingResults = GetObject("winmgmts://./root/cimv2").ExecQuery( strQuery ) ' Translate the query results to either True or False For Each objPingResult In colPingResults If Not IsObject( objPingResult ) Then Ping = False ElseIf objPingResult.StatusCode = 0 Then Ping = True Else Ping = False End If Next Set colPingResults = Nothing End Function

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on