sql server stored procedure

Question

0.00/5 (No votes)

See more:

Is it possible to say that a complex stored procedure never meets with time out error??

The stored procedure is going to be executed by .net command class.

Any reply will be apperciated....

Posted 8-Dec-11 2:36am

baisak

Add a Solution

3 solutions

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)

#realJSOP · Answer 1 · 2011-12-08T02:42:00

Solution 1

Of course a stored proc can be made to time-out. Assuming you have a proerly designed and constructed database, along with a stored proc that actually works, it shouldn't time-out. Try running the stored proc inside sql manager express and see how long it should take to run.

Posted 8-Dec-11 2:42am

#realJSOP

Ganesan Senthilvel · Answer 2 · 2011-12-08T02:43:00

Stored procedure is a set of Structured Query Language (SQL) statements with an assigned name that's stored in the database in compiled form so that it can be shared by a number of programs. The use of stored procedures can be helpful in controlling access to data (end-users may enter or change data but do not write procedures), preserving data integrity (information is entered in a consistent manner), and improving productivity (statements in a stored procedure only need to be written one time).

Itz nothing related to .NET framework

Eduard Lu · Answer 3 · 2011-12-08T17:41:00

Solution 3

Of course it might time-put. Use BEGIN TRY and BEGIN CATCH in SQL and make sure that you ROLLBACK those transactions when it fails or time-out.

Regards,
Eduard

Posted 8-Dec-11 17:41pm

Eduard Lu