Timeout problem

[Guest]

We have a Winform application in production. It has been compiled and installed on users' machines. One tasks in application keeps timing out. Is there anything we can do to increase timeout period without modifying source code and recompiling, redeploying this application? Connection string is stored in App.Config file. Thank you

 

[Miha Markic [MVP C#]]

Hi Lenn,

What exactly is timing out?
As for solution - it depends on the source of the problem.
It could be network, a bottleneck in the code, etc.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

We have a Winform application in production. It has been compiled and

installed on users' machines. One tasks in application keeps timing out. Is
there anything we can do to increase timeout period without modifying source
code and recompiling, redeploying this application? Connection string is
stored in App.Config file. Thank you

 

[Guest]

It times out when user starts a process that calls one particular stored procedure. This stored procedure retrieves 4 recordsets, one of the recordset is about 3k raws. It takes on average 20-30seconds to execute this sp in QA.
It doesn't timeout all the time. It does look like the timeout happens during increased users activity on the SQL server.

Hi Lenn,

What exactly is timing out?
As for solution - it depends on the source of the problem.
It could be network, a bottleneck in the code, etc.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

We have a Winform application in production. It has been compiled and

installed on users' machines. One tasks in application keeps timing out. Is
there anything we can do to increase timeout period without modifying source
code and recompiling, redeploying this application? Connection string is
stored in App.Config file. Thank you

 

[William \(Bill\) Vaughn]

Yes, I suspect this is the source of your problem. No, you need to increase
the CommandTimeout value in the Command used to execute the query. This
requires a recompile and redeploy.
However, I think a real solution is to design the application so it's not
pulling down 3-5k rows--but only the rows you need at the time. Fetch more
as needed instead of all at once.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

It times out when user starts a process that calls one particular stored

procedure. This stored procedure retrieves 4 recordsets, one of the
recordset is about 3k raws. It takes on average 20-30seconds to execute this
sp in QA.

It doesn't timeout all the time. It does look like the timeout happens

during increased users activity on the SQL server.

Hi Lenn,

What exactly is timing out?
As for solution - it depends on the source of the problem.
It could be network, a bottleneck in the code, etc.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

We have a Winform application in production. It has been compiled and

installed on users' machines. One tasks in application keeps timing out. Is
there anything we can do to increase timeout period without modifying source
code and recompiling, redeploying this application? Connection string is
stored in App.Config file. Thank you

 

[Guest]

Thanks. I guess, will have to redeploy.
The requirements are as such that 3k records are needed at once. The data is outputed into text files.

Yes, I suspect this is the source of your problem. No, you need to increase
the CommandTimeout value in the Command used to execute the query. This
requires a recompile and redeploy.
However, I think a real solution is to design the application so it's not
pulling down 3-5k rows--but only the rows you need at the time. Fetch more
as needed instead of all at once.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

It times out when user starts a process that calls one particular stored

procedure. This stored procedure retrieves 4 recordsets, one of the
recordset is about 3k raws. It takes on average 20-30seconds to execute this
sp in QA.

It doesn't timeout all the time. It does look like the timeout happens

during increased users activity on the SQL server.

Hi Lenn,

What exactly is timing out?
As for solution - it depends on the source of the problem.
It could be network, a bottleneck in the code, etc.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

We have a Winform application in production. It has been compiled and
installed on users' machines. One tasks in application keeps timing out. Is
there anything we can do to increase timeout period without modifying source
code and recompiling, redeploying this application? Connection string is
stored in App.Config file. Thank you

 

[William \(Bill\) Vaughn]

In that case, I would investigate DTS. It is dramatically faster than using
the ADO query tool to do the job.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

Thanks. I guess, will have to redeploy.
The requirements are as such that 3k records are needed at once. The data is outputed into text files.

Yes, I suspect this is the source of your problem. No, you need to increase
the CommandTimeout value in the Command used to execute the query. This
requires a recompile and redeploy.
However, I think a real solution is to design the application so it's not
pulling down 3-5k rows--but only the rows you need at the time. Fetch more
as needed instead of all at once.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

It times out when user starts a process that calls one particular

stored
procedure. This stored procedure retrieves 4 recordsets, one of the
recordset is about 3k raws. It takes on average 20-30seconds to execute this
sp in QA.

It doesn't timeout all the time. It does look like the timeout happens

during increased users activity on the SQL server.

:

Hi Lenn,

What exactly is timing out?
As for solution - it depends on the source of the problem.
It could be network, a bottleneck in the code, etc.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

We have a Winform application in production. It has been compiled and
installed on users' machines. One tasks in application keeps timing

out.
Is

there anything we can do to increase timeout period without

modifying
source

code and recompiling, redeploying this application? Connection string is
stored in App.Config file. Thank you