ExecuteDataSet() is taking long time and hence time out error

Question

0.00/5 (No votes)

See more:

Hi all,

I am using ExecuteDataSet() to fetch the data from Oracle database.
when I run the qury directly on the databse i fetches records in 20 sec.
but when i execute the query in c# using ExecuteDataSet() it taking very long time and giving time out error.

Please share your ideas.

this is the way I am calling the method.

ds = dataBase.ExecuteDataSet(dbCommand);

Posted 1-Aug-13 20:16pm

Sreepada1005

Updated 7-Feb-18 23:52pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Harshil_Raval · Accepted Answer · 2013-08-01T20:28:00

Solution 1

Hi,

Try to give timeout to dbcommand.

C#

dbCommand.CommandTimeout = 500;//As per your query taking time

I have one doubt that if your query successfully run in 20sec in db, then pls check in your code, there may be some issue.

Posted 1-Aug-13 20:28pm

Harshil_Raval

Comments

Sreepada1005 2-Aug-13 2:38am

Thnks for your response.

my command time out is 0.which means unlimited.Even I tried giving 600.
dbCommand.CommandTimeout = 0;

1st three execution s are fine.problem encounters from 4th or 5th execution.