SELECT*

SQL Script Copy SELECT rh.restore_date AS [RestoreTime], rh.destination_database_name AS [Database], CASE rh.restore_type WHEN 'D' THEN 'Full Database' WHEN 'I' THEN 'Differential' WHEN 'L' THEN 'Log' WHEN 'F' THEN 'File' WHEN 'G' THEN 'Filegroup' WHEN 'P' THEN 'Partial' WHEN 'V' THEN 'VerifyOnly' END AS [RestoreType], bs.backup_start_date AS [BackupMadeAt], bmf.physical_device_name AS [SourceFile], rh.user_name AS [RestoredBy] FROM msdb.dbo.restorehistory rh INNER JOIN msdb.dbo.backupset bs ON rh.backup_set_id = bs.backup_set_id INNER JOIN msdb.dbo.backupmediafamily bmf ON bs.media_set_id = bmf.media_set_id WHERE rh.destination_database_name = 'dbname' -- Change this ORDER BY rh.restore_date DESC ;

  What each part means Process ID 108 This is SQL Server’s internal process ID (not the same as SPID). It usually maps to a worker or session inside SQL Server that was terminated. You normally don’t troubleshoot this ID directly; it’s mostly for internal tracking. “was killed by hostname RAM1234” RAM1234 is the client machine name from which the kill originated. This is not the SQL Server host . It is typically: An application server A user workstation A job agent / automation server Or sometimes the SQL Server itself , if a local process did it 👉 So yes — in most cases this is the server where the application is running or where someone was connected from. Host process ID 7404 This is the Windows OS process ID (PID) on RAM1234 . It represents the client-side process that issued the KILL or caused the disconnect. Examples of what PID 7404 could be: sqlcmd.exe powershell.exe An application service (Java, .NET, etc.) ...