Skip to main content

Database changes with Audit Table


In Recent I faced the problem whenever we need to move the DB Changes to Production environment we have some table in the Development environment .we have added some columns to table in Development. we need to change definitions in production environment also .At this time we are some little bit of problem facing . Today I come up with the solution we need to create the DDL trigger on Database level. Whenever we are moving the DB Changes to Production environment we can cross check audit table.  

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

--Create Audit Table
 create table Audit
 (
 EventType nvarchar(max),
 Command nvarchar(max),
 Createdon datetime
 )
--Create DDL Trigger on Database
create  trigger AuditDBChanges
on database
for create_table,alter_table,drop_table
as
begin
 DECLARE
@EventData XML = EVENTDATA();
insert into Audit (EventType,Command,Createdon)
select     @EventData.value('(/EVENT_INSTANCE/EventType)[1]',   'NVARCHAR(100)'),
 @EventData.value('(/EVENT_INSTANCE/TSQLCommand)[1]', 'NVARCHAR(MAX)'),
  getdate()
end

--Add Marks column to Student Table
alter table Student add Marks int

-- drop table
drop table Student

--Check the Adit Information
 select * from Audit






-- Disable trigger from Databse
disable trigger AuditDBChanges on database

--Enable trigger from Databse
Enable trigger AuditDBChanges on database

--Drop trigger from Databse
drop trigger AuditDBChanges on database

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


Comments

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 ?...

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 ...