September 20, 2009 at 1:15 pm
Hi Everyone...
Why we are calling stored procedures as Stored Procedures ? what is the reason benind this ?
All the database objects have bee stored in the database only albeit we are calling only STORED Procedure as Stored procedure.
Thanks in Advance.
September 20, 2009 at 1:33 pm
you got me on this one...
I guess that's because this is almost the only PROCEDURal code that is allowed to do anything in the server: create or drop objects, alter data, etc...
All the rest are TSQL crippled code snippets...
September 21, 2009 at 6:37 am
Thanks for your reply...
Ss .. this might be the reason for that.
Anyother answer ?
September 21, 2009 at 6:40 am
As far as I know it's because you can write procedures and not store them or store the procedures.
It's just a reasonably descriptive name.
Why are you asking about it & not say, table valued user defined functions?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply