RE: ConnectionRead Timeout Problem

Hi Dimitar,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you are getting a Timeout exception
when using sp_proc_sel directly as the command text. If there is any
misunderstanding, please feel free to let me know.

According to SQL Server Books Online, if the first three characters of the
procedure name are sp_, SQL Server searches the master database for the
procedure. If no qualified procedure name is provided, SQL Server searches
for the procedure as if the owner name is dbo. To resolve the stored
procedure name as a user-defined stored procedure with the same name as a
system stored procedure, provide the fully qualified procedure name. You
can use databasename.dbo.sp_proc_sel as the command text and try again or
you can also try to change the name of the stored procedure by removing the
prefix sp_. For more information about this limitation, please check the
following link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
ea-ez_05ro.asp

Also, you can try to enlarge the value of cmd.CommandTimeout to see if more
commands can be executed within a transaction.

If that still doesn't work, you can try to start a trace using SQL Profiler
to see if the last command has been submitted to the server and check what
makes it timeout.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

.

Relevant Pages