Database

Rafferty Uy wrote:

Is it possible for triggers not to execute when the performance is poor?

Rafferty Uy wrote:

is it possible for the trigger to roll back the insert on table A if it fails

Rafferty Uy wrote:

How can I write TableAInsertTrigger in such a way that, if it fails, it will also roll back the AddToTableA SP?

CREATE PROCEDURE AddToTableA() AS
BEGIN
    BEGIN TRANSACTION
    INSERT INTO TableA VALUES(1, 'SomeValue')
    IF (@@ERROR <> 0) GOTO ERR_HANDLER
    COMMIT TRANSACTION
    RETURN 0

    ERR_HANDLER:
    ROLLBACK TRANSACTION
END

CREATE TRIGGER TableAInsertTrigger ON TableA FOR INSERT
BEGIN
    INSERT INTO TableB (SELECT * FROM INSERTED)
    
    -- do something else here, one that causes error
END

Rafferty Uy wrote:

In the above case, if I call AddToTableA() and since TableAInsertTrigger fails, it will roll back the inserts on both TableB (in the Trigger) and TableA (in the SP)?

Rafferty Uy wrote:

btw, thank you for helping

mobius111001 wrote:

Is any date between 01/01/2008 - 12/31/2015 in 11/21/2008 - 12/21/2009?

date1 = 01/01/2008 
date2 = 12/31/2015 
date3 = 11/21/2008 
date4 = 12/21/2009 

... date1 between date3 and date4 
or  date2 between date3 and date4
or  (date1 < date3 and date2 > date4) ...

SELECT CONCAT( 'ALTER TABLE ', Table_Name, ' CHANGE ...') 
FROM Information_Schema.Tables 
WHERE Table_Schema = 'YourSchema';