Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)

  • RE: Single Trigger on multiple tables

    No, because the original goal was to insert a row in a table. Functions cannot have side-effects and that includes inserting a row in a table.

    September 28, 2002 at 1:29 pm

    #437438

  • RE: Single Trigger on multiple tables

    OK, you just use the EXEC statement like that:

    EXEC pMyStoredProc

    If you want to use parameters or have a little error handling, your call would look more like something like that:

    DECLARE...

  • RE: Single Trigger on multiple tables

    What you could do to avoid redundancy and improve maintainability is putting your code in a stored proc and calling that SP from your 3 triggers. That way if you...

  • RE: Searching in stored procs code

    The code for stored procedures is stored in the syscomments system table, the following script should do the trick:

    --USE YourDatabase

    --GO

    SELECT

    o.name, c.text

    FROM

    syscomments c

    ...

  • RE: Specifying position when adding a column

    Like I said in my last post, I like to order columns in a business logical order, but primarily I had 100 tables that I needed to use with replication,...

  • RE: Specifying position when adding a column

    ok, guys, it's just that I needed to do add a column in the first position for like 100 tables, so I would have liked to be able to generate...

Viewing 6 posts - 1 through 6 (of 6 total)