Answer / guest

The pros are that you can implement additional
functionality and access data from DLLs from within SQL
Server. If you need to do something that can be done only
in C or C++, or if you have data that can be accessed only
outside of SQL Server, you can still provide a link to it.
The biggest con to extended stored procedures is that they
run in the same process space as SQL Server. So an errant
DLL could overwrite memory and cause SQL Server to crash or
even corrupt data. The biggest safeguard against these
problems is thorough testing of the procedure

How to Insert multiple rows with a single insert statement?

0 Answers  

---

What are the new data types are introduced in sql 2000?

0 Answers  

---

How to receive returning result from a query?

0 Answers  

---

What is function of CUBE ?

0 Answers   HCL,

---

What is #table in sql server?

0 Answers  

---

---

What is the difference between Stored Procedure , Function and Package, 1. how many blocks in Package and what are they.

5 Answers   IBM,

---

Wht is the difference between stored procedure and trigger

6 Answers   HCL, TCS,

---

How to delete existing triggers using "drop trigger"?

0 Answers  

---

Why do you need a sql server?

0 Answers  

---

What is default constraint in ms sql server?

0 Answers  

---

How to get the count of distinct records. Please give me the query?

8 Answers   Value Labs,

---

How to verify a user name with sqlcmd tool?

0 Answers  

---