.Net stored proc call drop out. -- dotnet ado.net

Amelia
6/30/2005 6:14:04 AM

We are experiencing a weird problem where a call to a stored proc using
native SqlClient connection class in a VB.Net app fails on one machine when
processing a large set of data (23,000 rows) BUT will always work on another
PC. We checked patching and both are (now) running SQL Server SP3a and also
the version of MDACs is 2.7 SP1 refresh. The other DLL's we use DTS and EXCEL
are deployed with the app. Small sets of data run fine on ALL machines all of
the time. The stored proc runs successfully when executed from SQL Query
Analyzer.

Has anyone experienced anything like this? Here's hoping! I'm running out of
ideas of things to check. Trying to trap the error returned a blank string?

Thanks

Cowboy (Gregory A. Beamer) - MVP
6/30/2005 8:00:03 AM

Increase the timeout. Most likely, the machine it is failing on is a bit more
loaded, has a lesser CPU, etc. and is failing. You will likely find that the
other machine is fairly close to the timeout, as well, but it is not failing
as it gets done within the window.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

[quoted text, click to view]

William (Bill) Vaughn
6/30/2005 2:15:43 PM

You say "processing". Are you using ADO to transport the data to the server?
If so why not use DTS or BCP which are designed for this? These tools can
import data from Excel as well.
Do both systems have the same hardware?
When a SP is compiled the first time its query plan is created based on the
parameters passed. This same plan is reused each time so when your SP is
complex or you pass different parameters, the QP might not match the data.
Try to force a recompile of the SP on execution.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
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.
__________________________________

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet ado.net

dotnet ado.net : .Net stored proc call drop out.