Answer / samba shiva reddy . m

Microsoft SQL Server provides the stored procedure mechanism to simplify the database development process by grouping Transact-SQL statements into manageable blocks.
Benefits of Stored Procedures

Why should you use stored procedures? Let's take a look at the key benefits of this technology:
Precompiled execution. SQL Server compiles each stored procedure once and then reutilizes the execution plan. This results in tremendous performance boosts when stored procedures are called repeatedly.
Reduced client/server traffic. If network bandwidth is a concern in your environment, you'll be happy to learn that stored procedures can reduce long SQL queries to a single line that is transmitted over the wire.
Efficient reuse of code and programming abstraction. Stored procedures can be used by multiple users and client programs. If you utilize them in a planned manner, you'll find the development cycle takes less time.
For example you are using some select statement 10 times in your application and your client is asked for change so you have to change 10 places.but if you use the Stored procedure
you have to change in one place and also you are using name of the stored procedure not the total select statement.
Enhanced security controls. You can grant users permission to execute a stored procedure independently of underlying table permissions.
Stored procedures are very similar to user-defined functions, but there are subtle differences. For more information, read Comparing Stored Procedures and User-Defined Functions.
we can't use the stored procedure name in select statement.

Structure

Stored procedures are extremely similar to the constructs seen in other programming languages. They accept data in the form of input parameters that are specified at execution time. These input parameters (if implemented) are utilized in the execution of a series of statements that produce some result. This result is returned to the calling environment through the use of a recordset, output parameters and a return code. That may sound like a mouthful, but you'll find that stored procedures are actually quite simple.
Example

Let's take a look at a practical example. Assume we have the table shown at the bottom of this page, named Inventory. This information is updated in real-time and warehouse managers are constantly checking the levels of products stored at their warehouse and available for shipment. In the past, each manager would run queries similar to the following:
SELECT Product, Quantity
FROM Inventory
WHERE Warehouse = 'FL'
This resulted in very inefficient performance at the SQL Server. Each time a warehouse manager executed the query, the database server was forced to recompile the query and execute it from scratch. It also required the warehouse manager to have knowledge of SQL and appropriate permissions to access the table information.

We can simplify this process through the use of a stored procedure. Let's create a procedure called sp_GetInventory that retrieves the inventory levels for a given warehouse. Here's the SQL code:
CREATE PROCEDURE sp_GetInventory
@location varchar(10)
AS
SELECT Product, Quantity
FROM Inventory
WHERE Warehouse = @location
Our Florida warehouse manager can then access inventory levels by issuing the command
EXECUTE sp_GetInventory 'FL'
The New York warehouse manager can use the same stored procedure to access that area's inventory.
EXECUTE sp_GetInventory 'NY'
Granted, this is a simple example, but the benefits of abstraction can be seen here. The warehouse manager does not need to understand SQL or the inner workings of the procedure. From a performance perspective, the stored procedure will work wonders. The SQL Sever creates an execution plan once and then reutilizes it by plugging in the appropriate parameters at execution time.

Now that you've learned the benefits of stored procedures, get out there and use them! Try a few examples and measure the performance enhancements achieved -- you'll be amazed!

Inventory Table
ID Product Warehouse Quantity
142 Green beans NY 100
214 Peas FL 200
825 Corn NY 140
512 Lima beans NY 180
491 Tomatoes FL 80
379 Watermelon FL 85

I will post indexes in next post.

Answer / trived.r

store proceder is T-SQL commend , in store proceders
baunch of commends and bunch of statement excuted at a time
know as store proceder.
ex :
select (avg)sal,ename from emp

we dont write evry time this commend

simply write of this commend insted of

write this commend (STORE PROCEDER)

CREATE PROC USD_AVGSAL FROM EMP
U EXECUTE N NUMER OF TIMES WITH THIS AND
EXEC USD_AVGSAL...........
Index is read from spcific recored or data know as index.
and index use of retrive data fast.faster excution.
syntax:
create non clusterd index cid_eid_emp

on emp(eid)
on primary.

How to loop through the result set with @@fetch_status?

0 Answers  

---

how we can store the value like that 001,003,023 etc in sql server 2005

7 Answers  

---

What is an entity-relationship diagram (erd)?

0 Answers  

---

How do I view a stored procedure in sql server query?

0 Answers  

---

What is the difference between distinct clause and group by clause?

2 Answers   HHH, Value Labs,

---

---

What are out-of-range errors with date and time literals?

0 Answers  

---

What is best institute to Learn DotNET And SQL in chennai?

0 Answers  

---

Why would you use sql agent?

0 Answers  

---

What is the purpose of indexing?

0 Answers  

---

what protocol both networks use? : Sql server database administration

0 Answers  

---

How do you delete duplicate rows in sql server?

0 Answers  

---

In performance wise distinct is good or group by is good? eg:select name from emp group by name; select distinct name from emp;

5 Answers   Infosys,

---