Originally posted by luciffer
I argues that point with my co-worker but he thought it would be less efficient to store the balance in another table and have triggers to increment/decrement the balance.
Looks like you have to pay the price somewhere . . .

Maybe if you rethink your data model it might help? I see 3 entities (draw, participant & ticket) and draw:ticket is m:n (I think) - so I would expect 4 tables.