When we are working with different versions of database, database professionals are comparing the objects between databases of SQL Server.
They must make sure about that all databases are in sync.

Using this T-SQL Script, you can compare two databases and find a list of unmatched objects like: Constraints, Tables, Views, Stored Procedure, Triggers.

Sample demonstration:
First, Create two sample databases:

CREATE DATABASE ABC
GO
CREATE DATABASE XYZ
GO

Create few sample tables in both the databases:

CREATE TABLE ABC.dbo.tbl_Test
(
	ID INT
	,MyDate DATE
)
GO

CREATE TABLE ABC.dbo.tbl_MyTest
(
	ID INT
	,Name VARCHAR(50)
)
GO

CREATE TABLE XYZ.dbo.tbl_Test
(
	ID INT
	,MyDate DATE
)
GO

CREATE TABLE XYZ.dbo.tbl_MyFinal
(
	ID INT
	,Name VARCHAR(50)
)
GO

T-SQL Script to compare objects between two databases:
According to your databases, You can change the name of @SourceDatabase and @DestinationDatabase.

DECLARE @SourceDatabase VARCHAR(50) 
DECLARE @DestinationDatabase VARCHAR(50) 
DECLARE @SQL VARCHAR(MAX) 
     
SELECT @SourceDatabase = 'ABC' 
SELECT @DestinationDatabase = 'XYZ'
     
SELECT @SQL = 
'
	SELECT 
		ISNULL(S.name,D.name) ObjectName
		,CASE  
			WHEN S.object_id IS NULL 
				THEN D.type_desc + '' is missing in the Source Database: '	+ @SourceDatabase + ''' 
			WHEN D.object_id IS NULL 
				THEN S.type_desc +  '' is missing in the Destination Database: ' + @DestinationDatabase + ''' 
		END ''Status'' 
	FROM 
	(
		SELECT * FROM ' + @SourceDatabase + '.SYS.objects  
		WHERE Type_desc not in (''INTERNAL_TABLE'',''SYSTEM_TABLE'',''SERVICE_QUEUE'')
	) AS S  
	FULL OUTER JOIN 
	(
		SELECT * FROM ' + @DestinationDatabase + '.SYS.objects  
		WHERE Type_desc not in (''INTERNAL_TABLE'',''SYSTEM_TABLE'',''SERVICE_QUEUE'')
	) AS D 
	ON S.name = D.name 
		AND S.type = D.type 
	ORDER BY isnull(S.type,D.type)
'  
EXEC (@Sql)

The Result:

ObjectName                         Status
------------------  -------------------------------------------------------
tbl_Test              NULL
tbl_MyFinal           USER_TABLE is missing in the Source Database: ABC
tbl_MyTest            USER_TABLE is missing in the Destination Database: XYZ

In this post, I am sharing a script for getting the list of Triggers in SQL Server. Periodically, we should do the auditing of database hidden triggers.

Because triggers are not good for database performance especially for OLTP system. Many times developers are creating triggers for testing purpose and later forget to drop those.

SQL Server: Encrypted DDL Trigger to Track all Database Changes

Execute the below script and get list of all triggers:

SELECT 
	sysobjects.name AS TriggerName 
	,USER_NAME(sysobjects.uid) AS TriggerOwner 
	,s.name AS TableSchema 
	,OBJECT_NAME(parent_obj) AS TableName 
	,OBJECTPROPERTY( id, 'ExecIsUpdateTrigger') AS Isupdate 
	,OBJECTPROPERTY( id, 'ExecIsDeleteTrigger') AS Isdelete 
	,OBJECTPROPERTY( id, 'ExecIsInsertTrigger') AS Isinsert 
	,OBJECTPROPERTY( id, 'ExecIsAfterTrigger') AS Isafter 
	,OBJECTPROPERTY( id, 'ExecIsInsteadOfTrigger') AS Isinsteadof
	,OBJECTPROPERTY(id, 'ExecIsTriggerDisabled') AS Isdisabled
FROM sysobjects 
INNER JOIN sysusers 
    ON sysobjects.uid = sysusers.uid 
INNER JOIN sys.tables t 
    ON sysobjects.parent_obj = t.object_id 
INNER JOIN sys.schemas s 
    ON t.schema_id = s.schema_id 
WHERE sysobjects.type = 'TR'

In this post, I am sharing one option to Disable / Enable the Foreign Key Constraint in PostgreSQL.

During data migration and testing purpose, Database Developer requires to disable Foreign key constraint of a Table.

Once you disable constraint, then later you might need to enable again, but during this exercise make sure that all your data changes are correct.

PostgreSQL does not provide any direct command or function to disable / enable the Foreign key constraints.

When you create any Foreign Key on the table, internally It creates a hidden trigger for check data integrity.
You should enable/disable the trigger for achieving disable foreign key constraint.

Create a sample Student Master table:

CREATE TABLE tbl_Students 
(
	StudID INTEGER PRIMARY KEY
	,StudName CHARACTER VARYING
	,StudClass CHAR(1)	
);

Insert few sample records in Student Master table:

INSERT INTO tbl_Students 
VALUES (1,'Anvesh','A')
,(2,'Neevan','B'),(3,'Jenny','C')
,(4,'Roy','C'),(5,'Martin','C');

Create a sample Student Marks table:

CREATE TABLE tbl_StudentMarks
(
	StudentMarkID INTEGER PRIMARY KEY
	,StudID INTEGER 
	,Sub1Mark SMALLINT
	,Sub2Mark SMALLINT
	,Sub3Mark SMALLINT	
	,CONSTRAINT fk_tbl_StudentMarks_StudID FOREIGN KEY (StudID) REFERENCES tbl_Students (StudID)
);

Try to insert data with StudID which does not belong to Student Master table:

INSERT INTO tbl_StudentMarks 
VALUES (1,6,50,60,90);

You will get a below error message:

ERROR:  insert or update on table "tbl_studentmarks" violates foreign key constraint "fk_tbl_studentmarks_studid"
DETAIL:  Key (studid)=(6) is not present in table "tbl_students".
********** Error **********

Disable all hidden triggers of a Student Mark table:

ALTER TABLE tbl_StudentMarks DISABLE TRIGGER ALL;

Now Again, try to insert same record:

INSERT INTO tbl_StudentMarks 
VALUES (1,6,50,60,90);

Once you did with your task, please enable all trigger of a table:

ALTER TABLE tbl_StudentMarks ENABLE TRIGGER ALL;

This is one of the important post for all PostgreSQL Database Administrator who are dealing with Bulk Insertion in their PostgreSQL Server.

We should optimize Bulk Insertion operation because It is also utilizing more system resources.

Few steps to increase the performance of Bulk Insertion:

• If It is only one time data load, remove all Index and create after INSERT. For regular Bulk Insertion, look into Index part and try to optimize it.
• Take a backup of all the Triggers and drop all the Triggers.
• Use COPY command instead of INSERT.
• If you can not use COPY command because of of INSERT multiple value, you should not give more than 1000 multiple values in single INSERT. All INSERT multiple values stored in the memory area which may decrease the INSERT performance.
• Disable other database logging process.
• If BULK INSERTION is running with a single transaction, you should also disable all FOREIGN KEYs and later you can enable it.
• Change synchronous_commit=off to reduce the cost of committing.
• Change Checkpoint default configuration, Increase the checkpoint_segments value.
• Increase the size of shared_buffers, effective_cache_size, work_mem.
• Prepared all statements on server side.
• Disable Auto-Vacuum on Table.
• Disable Auto Database Backup process.
• Increase the system resource (Memory, Disk, CPU), If it is required.
• Use SSD type of Disk for faster storage.

Note: Whatever you changed for BULK INSERTION, please do not forget to rollback after completion of BULK INSERTION.

In this post, I am sharing an important TSQL Script to find the different status like Enable, Disable of a SQL Server Database Trigger.

Database Trigger is a significant object because it is doing the operation in the background and manipulates defined DDL and DML commands.

As a Database Administrator, this is our responsibility to find out the different status of all running Trigger of a SQL Server Database.

Below is a script:

SELECT
	[T].[name] AS TableName
	,[TR].[name] AS TriggerName
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsTriggerDisabled') =1 
		THEN 'DISABLED' ELSE 'ENABLED' 
	END) AS TriggerStatus
	 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsInsertTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsInsertTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsFirstInsertTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsFirstInsertTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsLastInsertTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsLAStInsertTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsDeleteTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsDeleteTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsFirstDeleteTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsFirstDeleteTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsLastDeleteTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsLAStDeleteTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsUpdateTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsUpdateTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsFirstUpdateTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsFirstUpdateTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsLastUpdateTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsLAStUpdateTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsAfterTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsAfterTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsInsteadOfTrigger') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsInsteadOfTrigger
 
	,(CASE 
		WHEN OBJECTPROPERTY([TR].[object_id], 'ExecIsTriggerNotForRepl') =1 
		THEN 'No' ELSE 'Yes' 
	END) AS IsTriggerNotForReplication 
FROM sys.tables AS T
INNER JOIN sys.triggers AS TR
	ON [T].[object_id]=[TR].[parent_id]