Hi Leland,

See my private e-mail for detailed explanation.

>Hi Nadya,
>
>I'm not sure I follow you. What tables would be included in two table model, and what tables would be included in the three table model.
>
>It seem to me that you could work with either SP or asp to update, insert and delete to your tables. If your company has control of the database server, and there would be no need to build the app in a way that would allow it to work with any database or with different Enterprises then you could probably use stored procedures without any disadvantages. However, if SP becomes a significant part of the application, it would make it difficult to switch back-ends, because all the SPs would have to be re-written to the new database like Oracle or DB2.
>
>I'm not sure but I think when building your recordset, you can use either two or three tables to grab the data into a single recordset. If this isn't correct, someone jump in a let me know. In postgres I can build views from any number of tables and modify the view. Then I can submit an update and the view would update each respective table from which it was created.
>
>Personally I prefer to do all data manipulation through the application and to keep all commands SQL 92 compliant, if possible. I feel this would make the application easier to maintain and update. It also makes the app easier to debug since the SQL and application are in the same place. With SPs you would need to review that app and then review the SP in the database. This could cause confusion and is more error prone.
>
>SP also have some advantages. SPs may result in a lessor cost of execution, because the SQL is already compiled and the execution plan is already determine. MS SQL should use any indexes you provide automatically to speed performance. Also, MS SQL would take care of all record locking issue, so you wouldn't need to do anything in that area unless you wanted to use transactions. Again, transaction would work best within the app as opposed to SP. I really don't know what the net cost saving of executing SPs verus asp would be, or if it would even be relevant. Usually the user with his human limitations proves to be the limiting factor in determining the critical path regarding overall speed.
>
>LelandJ