Because in these systems, you rarely have the luxury of updating a single
table. More often than not you have to execute an operation that rolls
changes through a number of tables where the process might encompass a
half-dozen tables in queries, changes, inserts, deletes and logging. The SP
can be hundreds of lines long (or more often call a dozen smaller SPs).
These systems were never able to use the simplistic Update method created
for the simple one-table designs. DBAs (for the most part) don't even grant
direct table access for updates so these SPs have to be granted specific
permission to change these tables.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Sahil Malik said:
Bill,
I'm curious why you say more sophisticated applications tend to do this in
stored procs.
- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.malik/archive/2005/05/13/63199.aspx
--------------------------------------------------------------------------
--