修复损坏的 MS SQL 主数据库 - 无 SQL 客户端访问

修复损坏的 MS SQL 主数据库 - 无 SQL 客户端访问

对于任何重复,我深表歉意,但我感觉自己在第一个障碍面前失败了。

我有一台 MS SQL 2005 Server,它拒绝启动,而且我没有它的密码(包括“sa”密码),显然是因为主数据库已损坏(见日志)。我通过谷歌搜索错误消息找到了很多说明(见下文),例如,但它们似乎首先都涉及到能够运行 SQL 命令。

运行sqlcmd并输入SELECT * FROM sys.configurationsp; (return)(按照链接 1)没有输出。运行sqlcmd -S DVTEL(其中 DVTEL 是配置管理器中找到的 SQL Server 服务之一)失败,并出现连接超时。

错误信息:

从配置管理器启动服务器时:Could not start the SQL Server (DVTEL) on Local Computer. For more info, review the system event log. 或者:

> NET START MSSQL$DVTEL /F /T3608 The SQL Server (DVTEL) service is starting. The SQL Server (DVTEL) service could not be started. A system error has occurred. System error 1067 has occurred. The process terminated unexpectedly.

错误日志:

2015-06-22 09:42:06.78 Server (c) 2005 Microsoft Corporation. 2015-06-22 09:42:06.78 Server All rights reserved. 2015-06-22 09:42:06.78 Server Server process ID is 2896. 2015-06-22 09:42:06.78 Server Authentication mode is MIXED. 2015-06-22 09:42:06.78 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\ERRORLOG'. 2015-06-22 09:42:06.78 Server This instance of SQL Server last reported using a process ID of 1340 at 22/06/2015 09:26:16 (local) 22/06/2015 08:26:16 (UTC). This is an informational message only; no user action is required. 2015-06-22 09:42:06.78 Server Registry startup parameters: 2015-06-22 09:42:06.78 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\master.mdf 2015-06-22 09:42:06.78 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\ERRORLOG 2015-06-22 09:42:06.78 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\mastlog.ldf 2015-06-22 09:42:06.78 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2015-06-22 09:42:06.78 Server Detected 4 CPUs. This is an informational message; no user action is required. 2015-06-22 09:42:06.95 Server Error: 8313, Severity: 16, State: 1. 2015-06-22 09:42:06.95 Server Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled. 2015-06-22 09:42:06.95 Server Error: 3409, Severity: 16, State: 1. 2015-06-22 09:42:06.95 Server Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions. 2015-06-22 09:42:06.99 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. 2015-06-22 09:42:07.01 Server Database mirroring has been enabled on this instance of SQL Server. 2015-06-22 09:42:07.01 spid5s Starting up database 'master'. 2015-06-22 09:42:07.07 spid5s Error: 9003, Severity: 20, State: 1. 2015-06-22 09:42:07.07 spid5s The log scan number (288:224: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. 2015-06-22 09:42:07.07 spid5s 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.

相关内容