Forum Replies Created

Viewing 8 posts - 16 through 23 (of 23 total)

  • RE: Nested Transactions - Best Practice

    In this particular example, the trigger is for insert on an InvoiceItem table (e.g. it stores lines on an invoice). On insert, stock has to be allocated against each invoice...

  • RE: Nested Transactions - Best Practice

    Hey I've been playing around this morning, with some example SP and example triggers, trying to write an error handler and testing how to structure the try\catch blocks etc.

    So I've...

  • RE: Nested Transactions - Best Practice

    Well we don't really either, it's just that this DB is not in production yet and we're still heavily in development (with DB changes coming in every day) so I...

  • RE: Nested Transactions - Best Practice

    hmm, Ok Matt thanks.

    BEFORE triggers! I wish! Bloody SQL Server doesn't support them.

    My triggers used to be "INSTEAD OF", but yeah I wasn't too impressed with the whole maintenance...

  • RE: Nested Transactions - Best Practice

    Guys, your making me suck eggs here,

    Yes data integrity tasks on the most part can be modelled with PKs and FKs. Those that can't, can be modelled with triggers. I've...

  • RE: Nested Transactions - Best Practice

    Hi Jeff,

    Thanks for the input, but I think you may have miss-read my post, I said I was utilising triggers for data integrity tasks, not business rules.

  • RE: Nested Transactions - Best Practice

    Thanks for your reply Matt.

    Yes I agree with you in that nested transactions should be avoided, but I'm utilising triggers for a variety of data integrity tasks on top...

  • RE: Nested Transactions - Best Practice

    Well don't all talk at once now.

    Come on, this is not cutting edge stuff, someone out there must at the very least have an opinion?

Viewing 8 posts - 16 through 23 (of 23 total)