By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,242 Members | 1,084 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,242 IT Pros & Developers. It's quick & easy.

SQLAdapter not returning value

P: n/a
Hi,

I have an application written in .Net and my database is
SQLserver. In my application i am using SqlAdapters to
get the values from the database. But sometimes, values
are not returned properly to these adapters and there are
no exceptions also. At this time, all database queries
will fail and the solution to this is restart the machine
(the client, not the sqlserver)

Could this be a problem with the connection pooling?

How should i proceed to nail down the problem?

Thanks,
Lekshmi
..
Nov 19 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
lekshmi,
Try posting ur code!

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 19 '05 #2

P: n/a
Hi,

his is the code which i am using

public decimal[] RetrieveReturnRange()
{

decimal[] RangeValues = new decimal[2];

m_command.CommandText = "[sp_GetRange]";

m_command.CommandType = CommandType.StoredProcedure;
m_command.Connection = m_connection;

DataTable RefundValueDT = new DataTable();

m_adaptor.Fill(RefundValueDT);
DataRow[] dr = RefundValueDT.Select("","RefundValue");
return dr
}

the stored procedure should ideally return one column
which has 2 rows from a look up table. this table will
always have 2 rows. the application runs fine most of the
times. but some times, say twice in a week ( frequency
not constant) the application will start throwing errors.
the value returned from the stored procedure will be
either null or some junk value. at this time, all the
queries to the database fails and we have to restart the
server mostly. but there are times when the problem will
get resolved by its own (say, after some 15 minutes).
this procedure is only a sample. Since this is the most
commonly used procedure, in the application during the
problem time, most of the errors are thrown by this
procedure.

Could some one help me out?

Thanks,
Lekshmi
-----Original Message-----
lekshmi,
Try posting ur code!

*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
.

Nov 19 '05 #3

P: n/a
Then if the error is from the Sprocedure then try checking it out.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 19 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.