1. Functions must always return a value (either a scalar value or a table). Stored procedures may return a scalar value, a table value or nothing at all.
2. Functions can have only input parameters whereas Stored Procedures can have input/output parameters .
3. Functions can be called from Stored Procedure whereas Stored Procedures cannot be called from Function.
4. Stored Procedure allows SELECT as well as INSERT/UPDATE/DELETE statement whereas Function allows only SELECT statement.
5. Stored Procedures can not be utilized in a SELECT statement whereas Function can be embedded in a SELECT statement.
6. Stored Procedures cannot be used in the SQL statements anywhere in the WHERE/HAVING/SELECT section whereas Function can be.
7. The most important feature of stored procedures over function is to retention and reuse the execution plan while in case of function it will be compiled every time.
8. Functions that return tables can be treated as another rowset. This can be used in JOINs with other tables.
9. Exception can be handled by try-catch block in a Stored Procedure whereas try-catch block cannot be used in a Function.
10. We can go for Transaction Management in Stored Procedure whereas we can't go in Function.
11. Stored procedures are called independently, using the EXEC command, while functions are called from within another SQL statement
The .NET Framework and ASP.NET help you create web applications and services for Windows.
Subscribe to:
Post Comments (Atom)
React-select is very slow on larger list - Found solution - using react-window
I had more than 4000 items in searchable dropdownlist. I have used react-select but it was very slow. finally I found complete solution to ...
-
Today I will show you how to use new salesforce toolkit for .NET Application. Follows the steps: Step 1. Create a project with C# ASP.NET ...
-
Classic mode is a mode where IIS only works with ISAPI extensions and ISAPI filters directly. In fact, in this mode, ASP.NET is just an ISA...
Good one
ReplyDelete