Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-05-15 : 09:34:23
|
| Britt writes "Hi all,I am part of a group that is building a small web based course admin system as an undergraduate work and hope you can help help me with a desing problem. The system has to be multilayered in any of these two setups:1) asp code in IIS web server2) COM objects with SQL code3) SQL server with viewsOr1) asp code in IIS web server (maybe calling procedures directly)2) COM objects (if neccesary)3) SQL server with procedures (no views or tables available to the outside)Can anyone help me with, or point me to, a discussion on pros and cons with such systems?TIA, Britt" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-05-15 : 09:47:43
|
| You should lean towards the 2nd scenario. We have some links here that detail stored procedures and app design:http://www.sqlteam.com/FilterTopics.asp?TopicID=102http://www.sqlteam.com/FilterTopics.asp?TopicID=111Take a look as some ASP sites too, some of them have good case studies on this:www.4guysfromrolla.comwww.15seconds.comwww.asp101.comwww.learnasp.comwww.aspalliance.comwww.asptoday.com --costs money, usually lame articles, but when they're good, OH MAN!I personally use SQL stored procedures for the data side of the process; most of the developers who come to SQL Team do likewise. There are performance, security and maintainability benefits to stored procedures, most of these will be covered in any decent book on SQL Server or ASP. Once you start using stored procedures, you'll never go back! If ANYONE gives you advice against stored procedures, it is BAD advice; don't listen to them, I don't care if they have 900 years of experience building databases, they're smoking crack.Using the COM tier to handle data access is also a good idea, it makes your code more secure. I personally DON'T use custom COM object for data access, though I'm in the minority. You can get by without them, but I would recommend using COM unless you have a small app with only a few users, and writing COM code would be burdensome for you or your team. |
 |
|
|
|
|
|
|
|
Multilayered design