Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Transact-SQL (2005)
 Program Locking

Author  Topic 

Vinnie881
Master Smack Fu Yak Hacker

1231 Posts

Posted - 2007-10-31 : 19:44:45
I have a stored procedure that used to run fine from a .net app.

For some reason when I run that specific stored procedure, it no longer works from .net.

I am still able to run the procedure from SMS w/o issue on the same machine.

I checked the sys_processes table and it just says .net client awaiting command.

Any sugestions on why this might not be going through?



Is there a easy way to check and see all open connections, and manually close the connection I want?

Vinnie881
Master Smack Fu Yak Hacker

1231 Posts

Posted - 2007-10-31 : 20:31:59
Strange.... I dropped the procedure and re-created and now it works fine.. Any one have any insight as to what might have happend?
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-10-31 : 22:39:49
Did you get any error when you say 'no longer works'?
Go to Top of Page

Vinnie881
Master Smack Fu Yak Hacker

1231 Posts

Posted - 2007-11-01 : 00:18:59
No error, it just would eventually time out.

I set the time-out period to infinate after that, it would not do anything, but never received a error, just eventually needed to restart the program.

Like I said it works fine now though, it's very strange.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-11-01 : 22:35:34
If happens again, you can start profiler trace to see if sql get connection request at all.
Go to Top of Page
   

- Advertisement -