Client CommandTimeout Property.

  • Let me see if I can get this correct: I have a co-worker that is using a VB application on a client node to call a SP residing on the server node. The SP requires up to 15 minutes to complete. 30 seconds after the client VB application calls the SP the client side will timeout and kill the thread that called the SP.

    We have been looking at the 'CommandTimeout' Property and set it above and beyond the 30 second default without any success.

    We have tried configuring the VB application running on the client use a 'Connection.Udl' but when we changed the 'CommandTimeout' Property this threw an error.

    So we replaced the 'Connection.Udl' with a hard coded connection string and tired to use the 'CommandTimeout' Property but this does not affect the client connection time.

    Any ideas?

    Thank you.

    Kevin S.


    Kevin S.

  • Command timeout should do it, though I never change in the connection string but rather at the command object itself.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply