OK, chyba znalazłem, jest tam wiele plików, otworzyłem pierwszy i jest coś takiego:
2016-12-03 21:47:43.63 Server Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2016-12-03 21:47:43.64 Server (c) Microsoft Corporation.
2016-12-03 21:47:43.64 Server All rights reserved.
2016-12-03 21:47:43.64 Server Server process ID is 5180.
2016-12-03 21:47:43.64 Server System Manufacturer: 'Dell Inc.', System Model: 'Vostro 3550'.
2016-12-03 21:47:43.64 Server Authentication mode is MIXED.
2016-12-03 21:47:43.64 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG'.
2016-12-03 21:47:43.64 Server This instance of SQL Server last reported using a process ID of 2196 at 2016-12-03 21:46:10 (local) 2016-12-03 20:46:10 (UTC). This is an informational message only; no user action is required.
2016-12-03 21:47:43.64 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\mastlog.ldf
2016-12-03 21:47:43.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-12-03 21:47:43.64 Server Detected 4 CPUs. This is an informational message; no user action is required.
2016-12-03 21:47:43.73 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2016-12-03 21:47:43.78 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-12-03 21:47:43.79 spid7s Starting up database 'master'.
2016-12-03 21:47:43.81 spid7s Error: 9003, Severity: 20, State: 1.
2016-12-03 21:47:43.81 spid7s The log scan number (617:152:1) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2016-12-03 21:47:43.81 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
