Stored Procedures :
Stored procedures are extremely useful objects. Not only do they store T/SQL scripts for later execution, but they also provide us with an extremely important security barrier between the user interface and the database. The security barrier is used to prevent the users from needing SELECT, INSERT, UPDATE and/or DELETE rights directly to the database tables and views.
This is done through what is called permissions chaining. When a user has rights to execute a stored procedure they are given temporary rights to use the table objects within the procedures which are used by the table.
Creating stored procedures is very easy. Take your Transact SQL code and put it below the CREATE PROCEDURE command, and end the batch. Like all other database objects the name of the stored procedure must be unique within the schema (or owner for SQL 2000 and below). As an example lets create a stored procedure which returns the names of all the tables in the current database.
CREATE PROCEDURE ShowTables AS
SELECT schema_name(schema_id), name
As you can see the basic syntax is very simple. To run this stored procedure we simply run the stored procedure name.
In this way we can create and execute stored procedures...
Car Hire Los Angeles
| Car Rental Sanford