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 - 2004-05-06 : 09:43:47
|
| Nick writes "I've been wondering for a while which is better 'stored procedures' harnessing the power of SQL Server and probably a 'bigger' server as opposed to COM on a web server.I understand that the preferred architecture is 3-tier where you should have your ASP pages on one server, COM objects on another server and SQL on a third server but most people I come across have their web pages and COM on the same server and then SQL on a separate server. Surely harnessing the power of SQL using stored procedures must be a better option than COM or maybe I've just missed the point." |
|
|
DavidD
Yak Posting Veteran
73 Posts |
Posted - 2004-05-07 : 09:10:35
|
| Use COM objects to pass parameters to sql server, stored procedures on the server to do the actual work and then pass the results back to the COM object.RegardsDavid |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-05-07 : 10:40:06
|
| Stored procedures are for database access and interface between bussiness entities and the storage structure.The com objects are for manipulating the data and any procedural row by row or data validation type stuff.It is best to try to send all data to a stored procedure invloved in an update so that transactions do not have to be maintained from the com layer.The idea is that the stored procedures return resultsets in the best format for the com objects to manipulate the data.ASP code should be kept as short as possible just formatting probably.A big dependancy is on the experience available.ASP will probably be faster than the com object for database access but a lot slower for processing.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|