Re: [ADVANCED-DOTNET] SQL Timeout

2007-02-22 Thread J. Merrill
First -- people who read these messages as "threads" would appreciate it if you brought in a new topic by sending a new message to the group, rather than by replying to an existing message while changing the subject. When you say "the process takes an age to complete" you're not giving informat

Re: [ADVANCED-DOTNET] SQL Timeout

2007-02-22 Thread Pardee, Roy
From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Eric Means Sent: Wednesday, February 21, 2007 4:00 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] SQL Timeout You could always consider making publishing a batch process of some sort; the user clic

Re: [ADVANCED-DOTNET] SQL Timeout

2007-02-21 Thread Eric Means
You could always consider making publishing a batch process of some sort; the user clicking Publish or Save or whatever adds those nodes the queue, and a separate process (probably a Windows Service or something) actually performs the needed actions. This might be what you meant by "asynchronousl

Re: [ADVANCED-DOTNET] SQL Timeout

2007-02-21 Thread Mark Brackett
Best option is to tune the query or database to get it to run faster. If what you're asking the db to do can't run in under 60 seconds (which I think is the default timeout), then you probably need to reconsider doing it while the user is waiting anyways. --Mark Brackett -Original Message