In this article, I will try to give information about where Triggers are used most in SQL Server.

Triggers are used in SQL Server to automatically execute a set of SQL statements or stored procedures when specific database events occur, such as INSERT, UPDATE, or DELETE operations on a table. Triggers are commonly used for the following purposes:

1. Enforcing Business Rules: Triggers can be used to enforce business rules and data integrity constraints. For example, a trigger can be used to prevent users from deleting a record if it is referenced by other records in the database.
2. Auditing Changes: Triggers can be used to log changes made to database tables. For example, a trigger can be used to write a record to an audit trail table whenever a row is updated or deleted.
3. Replicating Data: Triggers can be used to replicate data from one database to another. For example, a trigger can be used to replicate new records inserted into a table in one database to a table in another database.
4. Updating Views: Triggers can be used to update views when underlying data is changed. For example, a trigger can be used to update a view that shows a list of employees whenever a new employee is added to the Employees table.
5. Notification: Triggers can be used to send notifications to users or applications when specific events occur in the database. For example, a trigger can be used to send an email to a supervisor whenever a new employee is added to the Employees table.

In summary, triggers are used in SQL Server for a variety of purposes, including enforcing business rules, auditing changes, replicating data, updating views, and sending notifications.

Good luck to everyone in business and life.

The post Where is Trigger Used Most in SQL Server? first appeared on MSSQL Query.

In this article, I will try to give information about the creation and updating of Trigger in SQL Server.

In SQL Server, in some cases, you may want to view the creation and update details of the Trigger.

You can easily do this using the code below.

SELECT o.name AS [Trigger Name],
       CASE
           WHEN o.type = 'TR' THEN
               'SQL DML Trigger'
           WHEN o.type = 'TA' THEN
               'DML Assembly Trigger'
       END AS [Trigger Type],
       sc.name AS [Schema_Name],
       OBJECT_NAME(parent_object_id) AS [Table Name],
       o.create_date [Trigger Create Date],
       o.modify_date [Trigger Modified Date]
FROM sys.objects o
    INNER JOIN sys.schemas sc
        ON o.schema_id = sc.schema_id
WHERE (
          type = 'TR'
          OR type = 'TA'
      );

When you run the above code, you will see a result similar to the one below.

As you can see, we have displayed the creation and updating details of the Trigger.

Good luck to everyone in business and life.

The post Viewing Trigger Creation and Update Detail in SQL Server first appeared on MSSQL Query.

In this article, I will try to give information about how to reactivate all Triggers in SQL Server.

In SQL Server you may want to re-enable all Triggers in some cases.

You can easily do this using the code below.

EXEC sp_MSforeachtable 'ALTER TABLE ? ENABLE TRIGGER ALL';

You can re-enable all triggers by running this code.

Good luck to everyone in business and life.

The post Re-Enable All Triggers in SQL Server first appeared on MSSQL Query.

In this article, I will provide information about creating triggers that prevent table creation in SQL Server.

In SQL Server, in some cases, we may not want a table to be created in the current database.

You can easily do this using the code below.

CREATE TRIGGER StopTableCreation
ON DATABASE
FOR CREATE_TABLE
AS
PRINT 'This database does not allow new tables.';
ROLLBACK TRANSACTION;

--Create Table Code

CREATE TABLE Table1
(
    ID INT
);

When you run the above code, you will see a result similar to the one below.

As you can see, we could not create a table.

Good luck to everyone in business and life.

The post Trigger Preventing Table Creation in SQL Server first appeared on MSSQL Query.

In this article, I will provide information about getting the list of disabled or active Triggers in the database in SQL Server.

In SQL Server, in some cases you may want to get the list of disabled or active Triggers.

You can easily do this using the code below.

SELECT TBL.name AS TableName,
       SCHEMA_NAME(TBL.schema_id) AS Table_SchemaName,
       TRG.name AS TriggerName,
       TRG.parent_class_desc,
       CASE
           WHEN TRG.is_disabled = 0 THEN
               'Enable'
           ELSE
               'Disable'
       END AS TRG_Status
FROM sys.triggers TRG
    INNER JOIN sys.tables TBL
        ON TBL.object_id = TRG.parent_id
           AND TRG.is_disabled = 1; --use this filter to get Disabled/Enabled Triggers

Good luck to everyone in business and life.

The post Getting List of Disabled or Enabled Triggers in Database in SQL Server first appeared on MSSQL Query.

In this section, I will talk about how to list active triggers in SQL Server.

In SQL Server, in some cases, it may be necessary to list active triggers for the database.

Using the code below, you can list your active triggers for your database.

SELECT TAB.name AS TabloAdi,
       TRIG.name AS TriggerAdi,
       TRIG.is_disabled AS Pasiflik
FROM [sys].[triggers] AS TRIG
    INNER JOIN sys.tables AS TAB
        ON TRIG.parent_id = TAB.object_id;

When you run the query, you will see a result like the one below.

As you can see, all active triggers are listed.

Good luck to everyone in business and life.

The post Listing Active Triggers in SQL Server first appeared on MSSQL Query.

In this article, I will give information about the procedure that show the script of all triggers in SQL Server.

In some cases, you may want to script all triggers in SQL Server.

You can do this easily with the help of the procedure below.

--Creating the Procedure

CREATE PROCEDURE [dbo].[SYS_ScriptAllTriggers]
    @ScriptMode int = 0
AS 
BEGIN

    DECLARE @script TABLE (script varchar(max), id int identity (1,1))

    DECLARE 
        @SQL VARCHAR(8000), 
        @Text            NVARCHAR(4000), 
        @BlankSpaceAdded INT, 
        @BasePos         INT, 
        @CurrentPos      INT, 
        @TextLength      INT, 
        @LineId          INT, 
        @MaxID           INT, 
        @AddOnLen        INT, 
        @LFCR            INT, 
        @DefinedLength   INT, 
        @SyscomText      NVARCHAR(4000), 
        @Line            NVARCHAR(1000), 
        @UserName        SYSNAME, 
        @ObjID           INT, 
        @OldTrigID       INT; 

    SET NOCOUNT ON; 
    SET @DefinedLength = 1000; 
    SET @BlankSpaceAdded = 0; 

    SET @ScriptMode = ISNULL(@ScriptMode, 0);

    -- This Part Validated the Input parameters   
    DECLARE @Triggers TABLE (username SYSNAME NOT NULL, trigname SYSNAME NOT NULL, objid INT NOT NULL); 
    DECLARE @TrigText TABLE (objid INT NOT NULL, lineid INT NOT NULL, linetext NVARCHAR(1000) NULL); 

    INSERT INTO 
        @Triggers (username, trigname, objid) 
    SELECT DISTINCT 
        OBJECT_SCHEMA_NAME(B.id), B.name, B.id
    FROM 
        dbo.sysobjects B, dbo.syscomments C 
    WHERE 
        B.type = 'TR' AND B.id = C.id AND C.encrypted = 0; 

    IF EXISTS(SELECT C.* FROM syscomments C, sysobjects O WHERE O.id = C.id AND O.type = 'TR' AND C.encrypted = 1) 
    BEGIN 

        insert into @script select '/*'; 
        insert into @script select 'The following encrypted triggers were found'; 
        insert into @script select 'The procedure could not write the script for it'; 

        insert into 
            @script 
        SELECT DISTINCT 
            '[' + OBJECT_SCHEMA_NAME(B.id) + '].[' + B.name + ']' --, B.id 
        FROM   
            dbo.sysobjects B, dbo.syscomments C 
        WHERE  
            B.type = 'TR' AND B.id = C.id AND C.encrypted = 1; 

        insert into @script select '*/'; 
    END; 

    DECLARE ms_crs_syscom CURSOR LOCAL forward_only FOR 
    SELECT 
        T.objid, C.text
    FROM   
        @Triggers T, dbo.syscomments C 
    WHERE  
        T.objid = C.id 
    ORDER  BY T.objid, 
        C.colid 
    FOR READ ONLY; 

    SELECT @LFCR = 2; 
    SELECT @LineId = 1; 

    OPEN ms_crs_syscom; 

    SET @OldTrigID = -1; 

    FETCH NEXT FROM ms_crs_syscom INTO @ObjID, @SyscomText; 

    WHILE @@fetch_status = 0 
    BEGIN 

        SELECT @BasePos = 1; 
        SELECT @CurrentPos = 1; 
        SELECT @TextLength = LEN(@SyscomText); 

        IF @ObjID <> @OldTrigID 
        BEGIN 
            SET @LineID = 1; 
            SET @OldTrigID = @ObjID; 
        END; 

        WHILE @CurrentPos != 0 
        BEGIN 
            --Looking for end of line followed by carriage return         
            SELECT @CurrentPos = CHARINDEX(CHAR(13) + CHAR(10), @SyscomText, @BasePos); 

            --If carriage return found         
            IF @CurrentPos != 0 
            BEGIN 

                WHILE ( ISNULL(LEN(@Line), 0) + @BlankSpaceAdded + @CurrentPos - @BasePos + @LFCR ) > @DefinedLength 
                BEGIN 
                    SELECT @AddOnLen = @DefinedLength - (ISNULL(LEN(@Line), 0) + @BlankSpaceAdded ); 

                    INSERT 
                        @TrigText 
                    VALUES 
                        ( @ObjID, @LineId, ISNULL(@Line, N'') + ISNULL(SUBSTRING(@SyscomText, @BasePos, @AddOnLen), N'')); 

                    SELECT 
                        @Line = NULL, 
                        @LineId = @LineId + 1, 
                        @BasePos = @BasePos + @AddOnLen, 
                        @BlankSpaceAdded = 0; 
                END; 

                SELECT @Line = ISNULL(@Line, N'') + ISNULL(SUBSTRING(@SyscomText, @BasePos, @CurrentPos - @BasePos + @LFCR), N''); 

                SELECT @BasePos = @CurrentPos + 2; 

                INSERT 
                    @TrigText 
                VALUES
                    ( @ObjID, @LineId, @Line ); 

                SELECT @LineId = @LineId + 1; 

                SELECT @Line = NULL; 
            END; 
            ELSE 
            --else carriage return not found         
            BEGIN 
                IF @BasePos <= @TextLength 
                BEGIN 
                    /*If new value for @Lines length will be > then the         
                    **defined length         
                    */ 
                    WHILE ( ISNULL(LEN(@Line), 0) + @BlankSpaceAdded + @TextLength - @BasePos + 1 ) > @DefinedLength 
                    BEGIN 
                        SELECT @AddOnLen = @DefinedLength - ( ISNULL(LEN(@Line), 0 ) + @BlankSpaceAdded ); 

                        INSERT 
                            @TrigText 
                        VALUES 
                            ( @ObjID, @LineId, ISNULL(@Line, N'') + ISNULL(SUBSTRING(@SyscomText, @BasePos, @AddOnLen), N'')); 

                        SELECT 
                            @Line = NULL, 
                            @LineId = @LineId + 1, 
                            @BasePos = @BasePos + @AddOnLen, 
                            @BlankSpaceAdded = 0; 
                    END; 

                    SELECT @Line = ISNULL(@Line, N'') + ISNULL(SUBSTRING(@SyscomText, @BasePos, @TextLength - @BasePos+1 ), N''); 

                    IF LEN(@Line) < @DefinedLength AND CHARINDEX(' ', @SyscomText, @TextLength + 1) > 0 
                    BEGIN 
                        SELECT 
                            @Line = @Line + ' ', 
                            @BlankSpaceAdded = 1; 
                    END; 
                END; 
            END; 
        END; 

        FETCH NEXT FROM ms_crs_syscom INTO @ObjID, @SyscomText; 
    END; 

    IF @Line IS NOT NULL 
        INSERT 
            @TrigText 
        VALUES
            ( @ObjID, @LineId, @Line ); 

    CLOSE ms_crs_syscom; 

    insert into @script select '-- You should run this result under dbo if your triggers belong to multiple users'; 
    insert into @script select ''; 

    IF @ScriptMode = 2 
    BEGIN 

        insert into @script select '-- Dropping the Triggers'; 
        insert into @script select ''; 

        insert into @script 
        SELECT 
            'IF EXISTS(SELECT * FROM sysobjects WHERE id = OBJECT_ID(''[' + username + '].[' + trigname + ']'')'
            + ' AND ObjectProperty(OBJECT_ID(''[' + username + '].[' + trigname + ']''), ''ISTRIGGER'') = 1)'
            + ' DROP TRIGGER [' + username + '].[' + trigname +']' + CHAR(13) + CHAR(10) 
            + 'GO' + CHAR(13) + CHAR(10)
        FROM   
            @Triggers; 
    END; 

    IF @ScriptMode = 0
    BEGIN   
        update 
            @TrigText 
        set 
            linetext = replace(linetext, 'CREATE TRIGGER', 'ALTER TRIGGER') 
        WHERE 
            upper(left(replace(ltrim(linetext), char(9), ''), 14)) = 'CREATE TRIGGER' 
    END

    insert into @script select '----------------------------------------------'; 
    insert into @script select '-- Creation of Triggers'; 
    insert into @script select ''; 
    insert into @script select ''; 

    DECLARE ms_users CURSOR LOCAL forward_only FOR 
    SELECT 
        T.username, 
        T.objid, 
        MAX(D.lineid) 
    FROM   
        @Triggers T, 
        @TrigText D 
    WHERE  
        T.objid = D.objid 
    GROUP BY    
        T.username, 
        T.objid 
    FOR READ ONLY; 

    OPEN ms_users; 

    FETCH NEXT FROM ms_users INTO @UserName, @ObjID, @MaxID; 

    WHILE @@fetch_status = 0 
    BEGIN 

        insert into @script select 'setuser N''' + @UserName + '''' + CHAR(13) + CHAR(10); 

        insert into @script 
        SELECT 
            '-- Text of the Trigger' = 
            CASE lineid 
                WHEN 1 THEN 'GO' + CHAR(13) + CHAR(10) + linetext 
                WHEN @MaxID THEN linetext + 'GO' 
                ELSE linetext 
            END 
        FROM   
            @TrigText 
        WHERE  
            objid = @ObjID 
        ORDER  
            BY lineid; 

        insert into @script select 'setuser'; 

        FETCH NEXT FROM ms_users INTO @UserName, @ObjID, @MaxID; 
    END; 

    CLOSE ms_users; 

    insert into @script select 'GO'; 
    insert into @script select '------End ------'; 

    DEALLOCATE ms_crs_syscom; 
    DEALLOCATE ms_users; 

    select script from @script order by id

END


--Use of the Procedure 

EXEC dbo.SYS_ScriptAllTriggers

When you create and run the procedure, you will get a result like the one below.

As you can see, the script of all triggers has been created.

Good luck to everyone in business and life.

The post Procedure to Show Script of All Triggers in SQL Server first appeared on MSSQL Query.

In this article,

I will give information about how to enable All Triggers in SQL Server.

In SQL Server, in some cases, you may want to enable all triggers.

You can do this easily with the help of the code below.

--Enable All Triggers in SQL Server  

sp_msforeachtable 'ALTER TABLE ? ENABLE TRIGGER all'

--Let's check the triggers 

SELECT name AS TriggerName,
       is_disabled AS DisabledStatus
FROM sys.triggers
WHERE type = 'TR';

When you run the code, you will get a result like the one below.

As you can see, all triggers are enabled.

Good luck to everyone in business and life.

The post Enable All Triggers in SQL Server first appeared on MSSQL Query.

In this article,

I will give information about how to disable All Triggers in SQL Server.

In SQL Server, in some cases, you may want to disable all triggers.

You can do this easily with the help of the code below.

--Disable All Triggers in SQL Server  

sp_MSforeachtable 'ALTER TABLE ? DISABLE TRIGGER all';

--Let's check the triggers 

SELECT name AS TriggerName,
       is_disabled AS DisabledStatus
FROM sys.triggers
WHERE type = 'TR';

When you run the code, you will get a result like the one below.

As you can see, all triggers are disabled.

Good luck to everyone in business and life.

The post Disable All Triggers in SQL Server first appeared on MSSQL Query.

In this article, I will give information about how to list All Triggers in SQL Server.

In SQL Server you may want to list all Triggers in some cases.

You can do this easily with the help of the code below.

SELECT  
    name AS TriggerName,
	is_disabled AS DisabledStatus    
FROM 
    sys.triggers  
WHERE 
    type = 'TR';

When you run the code, you will get a result like the one below.

As you can see, all triggers are listed.

Good luck to everyone in business and life.

The post Listing All Triggers in SQL Server first appeared on MSSQL Query.