A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.
we are developing an asp.net web application.There are some system actions which need to run on database server(could be same as web server).These actions will be multithreaded,and will update some tables.Some actions will need to run continously,and some actions run after some interval--every month,or once daily.Should I implement these actions in database using stored procedures,or in an application using .net.What factors should we consider to decide?
Thursday, July 26, 2007
In a vanilla asp.Net + MS SQL Serve 2000/2005 implementation options could include
- Windows service
Consideration points are
- "action" behaviour: expected load on DB, processor, network, possible table locks
- regular DB performance reuirements and possiblity for "scheduled maintenance" time
- amount of processed data (by a regular DB load and by "actions") and DB design
- other (replication, server deployment etc.)
The thing, that you want to go with custom multithreaded implementation makes me think that there are some uncommon non-functional requirements at play.
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz