Re: When and when not to create SP/triggers

You can only reduce network traffic, when you have a client/server=20 application. But if application and database server are running on the=20= same machine, this is no effect. You should use triggers, to manipulate data depending on other data=20 manipulation (e. g. updating a sum table, after insert, update or=20 delete of a row) You should use stored procedures to take business rules from the=20 application. The best application uses views to get data, stored=20 procedures to update data. In that case, it is much easier to port=20 your application to another database. Greetings volker >>>>>>>>>>>>>>>>>> Urspr=FCngliche Nachricht <<<<<<<<<<<<<<<<<< Am 19.12.97, 00:03:08, schrieb kponn@aol.com (KPonn) zum Thema When=20 and when not to create SP/triggers: > Hi, >=20 > I am having trouble deciding when to (or when not to) create stored=20= procedures > and/or triggres. I know they are useful and there is overhead=20 involved. We have > PB application and all PB developers bug the hell out of me to create = triggers > and SPs. How do I decide if an SP or trigger should be created or not = created. > When I ask PB people why do you need it, I get "to reduce network=20 traffic" > response. How can I get a better grip on this issue (books are not=20= helping me > much!) ? >=20 > Thanks. > Keith