In this post, I am sharing one T-SQL Script to find SQL Server USER LOGIN Information.

As a DBA, we should check the USER LOGIN Information to make sure about the user expiration, password expiration.
Using password expiration information, you can also notify the user before its password expires.

SELECT 
	SL.name AS LoginName 
	,LOGINPROPERTY (SL.name, 'PasswordLastSetTime') AS PasswordLastSetTime 
	,LOGINPROPERTY (SL.name, 'DaysUntilExpiration') AS DaysUntilExpiration 
	,DATEADD(dd, CONVERT(int, LOGINPROPERTY (SL.name, 'DaysUntilExpiration')) 
				, CONVERT(datetime, LOGINPROPERTY (SL.name, 'PasswordLastSetTime'))) AS PasswordExpiration 
	,SL.is_policy_checked AS IsPolicyChecked 
	,LOGINPROPERTY (SL.name, 'IsExpired') AS IsExpired 
	,LOGINPROPERTY (SL.name, 'IsMustChange') AS IsMustChange 
	,LOGINPROPERTY (SL.name, 'IsLocked') AS IsLocked 
	,LOGINPROPERTY (SL.name, 'LockoutTime') AS LockoutTime 
	,LOGINPROPERTY (SL.name, 'BadPasswordCount') AS BadPasswordCount 
	,LOGINPROPERTY (SL.name, 'BadPasswordTime') AS BadPasswordTime 
	,LOGINPROPERTY (SL.name, 'HistoryLength') AS HistoryLength 
FROM sys.sql_logins AS SL 
WHERE is_expiration_checked = 1 
ORDER BY LOGINPROPERTY (SL.name, 'PasswordLastSetTime') DESC

A PostgreSQL Fatal error like role or username does not exist. This is a very common error which is facing by PostgreSQL Users.

Actually, this is happening because of misconfiguration of System username and Database Username.

Most of the Linux users are trying to log in PostgreSQL using root user. But actually, this is wrong.

You will need to become the operating system user under which PostgreSQL was installed to create the first user account.

Generally, the default user name is Postgres and default database is also Postgres.
Once you install PostgreSQL on Linux, you should set the password for the Postgres user which is the default super user of PostgreSQL.

Please do not try to log in with any other default Linux or Unix system user name.

Set password for the default Postgres user:

sudo passwd postgres

Create another role using “postgres”:
Creating new role “dbrnd”. -p = set the password and -d = allow to create database.

sudo -u postgres createuser dbrnd -d -P

PostgreSQL: How to Install PostgreSQL 9.4 on Ubuntu 14.04?

PostgreSQL: How to Install PostgreSQL 9.6 on Ubuntu 16.04?

SQL Server provides different types of database auditing option like: CDC, Database Audit.
Recently, I have shared one article about, change your database DDL changes using Encrypted DDL triggers.

SQL Server: Encrypted DDL Trigger to Track all Database Changes

Database Administrators are responsible for database security and Periodically, They have to track all the database related changes and make sure that everything is working fine.

But still sometimes, I used to track database changes from the SQL Server log files using fn_dblog().
I am sharing one way to find a person who dropped a table and also can get the name of that dropped table without enabling any auditing option of SQL Server.

Script to find the log of dropped objects:

Using this script, you can find a list of dropped tables and login name information, but you cannot get table name directly.
You can find the transaction id for each record and using this transaction ID, you can find the table name.

SELECT 
	[Transaction Id]
	,[Begin Time]
	,SUSER_SNAME ([Transaction SID]) AS [LoginName] 
FROM fn_dblog (NULL, NULL)  
WHERE [Transaction Name] = N'DROPOBJ';

Find Table name using TransactionID:

SELECT TOP 1 
	[Lock Information] 
FROM fn_dblog (NULL, NULL)  
WHERE [Transaction Id] = '0000:0015d6b3'  
AND [Lock Information] LIKE '%SCH_M OBJECT%';

The result:
To get the table name, you can copy the number and search into sys.objects table.

HoBt 0:ACQUIRE_LOCK_SCH_M OBJECT: 8:1015674666:0

Find your dropped table:
Please do not start to search your dropped table in your current database because Table already dropped.
You must restore the last backup of the database and you should search your dropped table in that database.

SELECT *FROM sys.objects 
WHERE Object_ID ='1015674666'

In this post, I am going to share one of the common error which is faced by most of the SQL Server DBA when they are migrating database from one server to another server.

Error 15023: User already exists in the current database. This basically the problem of Orphan users, which exists as a Database Login, but no longer exists in Master Database.

For example, I have migrated one database and user “dbrnd” exists in that database. In that new server, now I am going to create “dbrnd” login with assignment of that database.
Which threw an error like user already exists in the current database.

The simple solution is to map SID between Database login and Master Login.
Step 1: Identified orphaned users of your restored database.

SELECT 
	[dp].[type_desc]
	,[dp].[SID]
	,[dp].[name] AS UserName
FROM sys.database_principals AS dp  
LEFT JOIN sys.server_principals AS sp  
    ON [dp].[SID] = [sp].[SID]
WHERE [sp].[SID] IS NULL  
    AND [dp].[authentication_type_desc] = 'INSTANCE';

Step 2: Select any of that SID and try to find in sys.sql_logins table. If you do not find any match record, that user is orphaned.

SELECT [sid] 
FROM sys.sql_logins;

Step 3: Create manual login and map your missing SIDs:

CREATE LOGIN Login4Orphaned 
WITH PASSWORD = 'test123*1',  
SID = 0x088232135A0AAF44A2D1B18DCC280E44;

Step 4: Now, create user for this and a make your orphaned user as specific user:

ALTER USER MyUser123 WITH Login = Login4Orphaned;