Skip to main content

Restrict SP_ (Naming convention) with DDL Trigger

Sometimes naming convention also impact the performance problem in SQL SERVER. Whenever we creating the stored procedures we are giving the name just like SP_Get_Customer. SP_ it first checks the Master Database system procedures. All the system procedures stored in Master Database.
In this article we do not allow SP_ whenever stored procedure creating by using DDL Trigger.

--Create Student Table
create table Student
(             
                id int identity(1,1) ,
                Name varchar(100)
)

--Create DDL Trigger on Database
create  trigger Restrict_Sp_NameConvenction
on database
for create_Procedure
as
begin
declare @EventData XML = EVENTDATA(),@ObjectName Nvarchar(100);
select    @ObjectName=@EventData.value('(/EVENT_INSTANCE/ObjectName[1]','NVARCHAR(100)');
                if(substring(@ObjectName,1,3)='sp_')
                begin
                                raiserror('Procedure name can not be start with sp_',16,1)
                                rollback;
                end
end

--Create Stored Procedure Name starts with sp_
create procedure sp_Get_Student
 as
 begin
                select * from Student
 end

Msg 50000, Level 16, State 1, Procedure Restrict_Sp_NameConvenction, Line 10
Procedure name can not be start with sp_
Msg 3609, Level 16, State 2, Procedure sp_Get_Student, Line 1
The transaction ended in the trigger. The batch has been aborted.

--Create Stored Procedure Name does not starts with sp_
create procedure usp_Get_Student
 as
 begin
                select * from Student
 end

--Command(s) completed successfully.
  
 drop procedure sp_Get_Student

-- Disable trigger from Databse
disable trigger Restrict_Sp_NameConvenction on database

--Enable trigger from Databse
Enable trigger Restrict_Sp_NameConvenction on database

--Drop trigger from Databse
drop trigger Restrict_Sp_NameConvenction on database

--For more information about trigger event types
 select * from sys.trigger_event_types
Labels:

Comments

Post a Comment

Popular posts from this blog

Coalesce function

Coalesce function returns the first non-null value among the arguments. Syntax: Coalesce (expression [,..n]) Here is example using Coalesce function Example 1 DECLARE @Str1 varchar ( 10 ), @str2 varchar ( 20 ), @Str3 varchar ( 20 ) SET @Str2 = 'Sql' , @Str3 = 'Server' SELECT COALESCE ( @Str1 , @str2 , @Str3 ) As [Coalesce] In above example @Str2 value is ‘Sql’ , @str3 value is ‘Server’  and @str1 values is Null because it not assigned any value . Output: It return’s “Sql” because Coalesce function return’s first non null value. Example 2: Coalesce in select statement. IF OBJECT_ID ( 'Employee' , 'U' ) IS NOT NULL DROP TABLE Employee CREATE TABLE Employee (   ID INT IDENTITY ( 1 , 1 ) PRIMARY KEY ,   NAME VARCHAR ( 20 ),   SALARY INT ) INSERT INTO Employee   ( NAME , SALARY ) VALUES ( 'Rakesh' , 5000 ),(NULL, 6000 ),( 'Naresh...
1 comment
Read more

Views in real time senario

Views are nothing but saved select query. Views nothing but virtual table on top of physical table. Views can contain rows and columns .views is not stored data. The main use of view is hiding some rows data or some columns. There are two types of views: System defined view. User defined view. System Defined view: System defined view is categorized into 3 types System defined views can discuses in future articles. User defined views There are two types of user defined views. Simple View: A simple view is nothing but just single saved select statement. create table Emp ( ID int identity ( 1 , 1 ), Name varchar ( 20 ), Department varchar ( 20 ) ) insert into Emp ( Name , Department ) values ( 'rakesh' , 'software' ),( 'raju' , 'bpo' ),( 'ali' , 'software' ) I have created “Emp” table with above following ...
Post a Comment
Read more