A typical interview question for SQL DBA is, How to get the User Name, who created Database Backup?

Don’t prepare your self for the hard questions, I took many interviews, and most of the DBA doesn’t know about this basic info. (Including senior DBA)

I already shared information about RESTORE HEADERONLY, but here I am again sharing the direct question and answer which is useful for interviews.

If you want to know any information about database backup, without restoring the database you can get those details using RESTORE HEADERONLY.

Check the below command:
This is my test backup path, in the result, you can get a column like a UserName which who created the database backup.

RESTORE HEADERONLY FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL13.DBRND\MSSQL\BACKUP\dbrnd.bak'

In this post, I am sharing a DBA Script for checking the status of running backup in SQL Server.

I already shared different types of DBA Scripts on SQL Database Backup and Restore. Because the Database Backup and Restore is a primary task for any SQL DBA.

SQL Server: Script to find Last Backup Time for All Databases

SQL Server: Script to find Estimated Finish Time of The Backup Database

SQL Server: Script to find all Backup History Information

Using the below script, you can find the status of running database backup:

SELECT 
	A.NAME AS DatabaseName
	,B.TOTAL_ELAPSED_TIME/60000 AS Running
	,B.ESTIMATED_COMPLETION_TIME/60000 AS Remaining
	,B.PERCENT_COMPLETE 
	,(SELECT TEXT FROM sys.dm_exec_sql_text(B.SQL_HANDLE)) AS SQLCommand 
FROM MASTER..SYSDATABASES A, sys.dm_exec_requests B
WHERE A.DBID=B.DATABASE_ID 
   AND B.COMMAND LIKE '%BACKUP%'
ORDER BY B.PERCENT_COMPLETE  DESC
	,B.TOTAL_ELAPSED_TIME/60000 DESC

SQL Server Error:
Msg 3183, Level 16, State 2, Line 1
RESTORE detected an error on page (8888:65987423) in database “my_db” as read from the backup set

While restoring a SQL Server database from the backup file (.bak file), I got above error. It looks like a database backup corrupted for particular data page.

Following are different reasons behind the error 3183:

• The backup file got corrupted
• Unavailability of free space on temporary disk
• Maybe backup file harm by the viruses
• Trying to restore a backup on a server with lower version than the backup created
• Failure of any hardware or bad sector of hard drive

The possible solutions are:

• You should try RESTORE VERIFYONLY to see more information about the backup failure
• Verify the source database, use DBCC CHECKDB(‘DatabaseName’) WITH NO_INFOMSGS, ALL_ERRORMSGS on the server the backup was taken on and try to backup it again
• You could try using RECOVER DATABASE WITH CONTINUE_AFTER_ERROR with the backup command, then run a DBCC CHECKDB on the database