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

SP_MSForeachtable

Some times we need to query on the all the tables in one data base single statement. We use SP_MSForeachtable this is known as undocumented stored procedures . These all are system stored procedures. These stored procedures is place in Master database. NOTE: Please do not run all these queries in Production environment Example: create database UnDocumentedStoredProcedure use UnDocumentedStoredProcedure create table Emp ( ID int identity ( 1 , 1 ), Name varchar ( 50 ), Salary int ) insert into Emp ( Name , Salary ) values ( 'rakesh' , 8000 ),( 'raju' , 9000 ) create table Dept ( ID int identity ( 1 , 1 ), DeptName varchar ( 100 ) ) insert into Dept ( DeptName ) values ( 'CSE' ),( 'IT' ) We are created new database and also created some table with some dummy data. Select all tables data: exec sp_MSForeachtable 'select * from ?...
1 comment
Read more

SET ROWCOUNT

Stop the processing after the number of rows has been affected. Example: Step-1: Create the Table and insert some sample data. CREATE TABLE STUDENT ( ID INT IDENTITY ( 1 , 1 ) PRIMARY KEY , STUDENTNAME VARCHAR ( 100 ) NOT NULL , LIVINGLOCATION VARCHAR ( 100 ) NULL ) INSERT INTO STUDENT ( STUDENTNAME , LIVINGLOCATION ) SELECT 'Rakesh' , 'Hyderabad' UNION ALL SELECT 'Raju' , 'Delhi' UNION ALL SELECT 'Madhu' , 'Hyderabad' UNION ALL SELECT 'Naresh' ,NULL UNION ALL SELECT 'Venaktesh' , 'Chennai' In above Insert Statement we inserted 5 sample records. Step-2: Using SET ROWCOUT SET ROWCOUNT 3 ; SELECT * FROM STUDENT ORDER BY ID DESC It will affected 3 rows after that processing has been stopped. Step-2: Using SET ROWCOUT 0 SET ROWCOUNT 0 ; SELECT * FROM STUDENT ORDER BY ID DESC ...
7 comments
Read more