Is it possible for a table to have more than one trigger? Each trigger would call its own stored procedure.

Does it make sense to have more than one trigger on a table?

Would this have an impact on performance?

Yes; they're fired in the order that they're created.
Sometimes, but only you can decide.
Yes, so you'll need to determine if the cost is justified. The impact on performance depends on what the trigger/stored proc is doing.

You also need to look at it from a maintenance point of view. Since you can only influence the order the triggers are fired in by when they are created, you might have a problem if one of them needs to be changed. Either you change the one and the firing order is now different, or you have to recreate all of them is the order you want. It would be much simpler to have just one trigger with the SP calls in the order you want.

Andy

If the triggers are not too complex, you would just shift the problem from the trigger-creation to the stored procedure definition.

And please do your homework before creating multiple triggers on 1 table. I worked at a client that prohibited triggers because their experience convinced them that DB2 triggers were performance killers. Seems some genious created 100, that's right, 100 triggers on a table each calling a stored procedure and then everybody wondered why everything slowed down. How this ever made it to production is a testament to the unstoppable force of idiocracy.