> We are designing a system and have to decide whether to add as much of the
> code as possible as stored procedures. Or should we stay away from stored
> procedures as much as possible.
This is all IMO....
SP's and triggers should be used as first preference for 'data logic' (e.g.
ref integrity and generally keeping the data 100% intact), regardless of the
type or architecture of you application
Whether or not 'business logic' belongs in SP's/triggers depends on the
architecure of your application. If I was developing a 3-tier system (either
physical or logical), all the business logic would be in my code in the
middle tier, but if I was developing a 2-tier system, my first preference
would be putting all the business logic in the SP's/Triggers, and if I was
doing a 'desktop'/single user app, I would probably put it all in my code.
Phil
--
Discover a lost art - play Marbles
May 2004
www.marillion.com
ICQ: 760757 | AIM: pjshrimpton | Y!: pjshrimpton | pjshrimpton@...