Erro iniciar base de dados SQL, em win sql 2005 (NEXT 2008)

Provenzano

Provenzano

Power Member
Utilizo o programa NExt 2008 para a emissão de facturas. Um dia ao abri-lo deparo-me com um erro, a dizer que o servidor sql não existe, ou algo do genero..

Vou ao "sql server configurator" e ao tentar iniciar manualmente a bd aparece-me a mensagem:
sqlservererrorgx8.jpg


Verificando os logs do servidor vejo la:
Código: 
2008-07-23 17:49:07.97 Server      Microsoft SQL Server 2005 - 9.00.3068.00 (Intel X86) 
    Feb 26 2008 18:15:01 
    Copyright (c) 1988-2005 Microsoft Corporation
    Express Edition on Windows NT 6.0 (Build 6001: Service Pack 1)

2008-07-23 17:49:08.00 Server      (c) 2005 Microsoft Corporation.
2008-07-23 17:49:08.00 Server      All rights reserved.
2008-07-23 17:49:08.00 Server      Server process ID is 2228.
2008-07-23 17:49:08.00 Server      Authentication mode is MIXED.
2008-07-23 17:49:08.00 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$NEXT\LOG\ERRORLOG'.
2008-07-23 17:49:08.00 Server      This instance of SQL Server last reported using a process ID of 796 at 23-07-2008 15:22:10 (local) 23-07-2008 14:22:10 (UTC). This is an informational message only; no user action is required.
2008-07-23 17:49:08.00 Server      Registry startup parameters:
2008-07-23 17:49:08.00 Server           -d C:\Program Files\Microsoft SQL Server\MSSQL$NEXT\Data\master.mdf
2008-07-23 17:49:08.00 Server           -e C:\Program Files\Microsoft SQL Server\MSSQL$NEXT\LOG\ERRORLOG
2008-07-23 17:49:08.00 Server           -l C:\Program Files\Microsoft SQL Server\MSSQL$NEXT\Data\mastlog.ldf
2008-07-23 17:49:08.10 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-07-23 17:49:08.10 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2008-07-23 17:49:08.29 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.
2008-07-23 17:49:08.35 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-07-23 17:49:08.36 Server      Database mirroring has been enabled on this instance of SQL Server.
2008-07-23 17:49:08.36 spid5s      Starting up database 'master'.
2008-07-23 17:49:10.01 spid5s      Error: 9003, Severity: 20, State: 9.
2008-07-23 17:49:10.01 spid5s      The log scan number (160:20: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. 
2008-07-23 17:49:10.01 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.

já tentei colocar la uma copia que tinha feito da bd, manualmente, copiando a pasta, e nao consigo iniciar a bd.
 
nao actualizei.. a unica coisa que me aconteceu foi quebra de energia e pelo que estive agora a procurar na net pode ter sido a causa.
 
Algo tipo isto:

27. P. como fazer I reconstruir a base de dados principal?

A: Para reconstruir a base de dados principal de uma instância do SQL Server 2000, utilize o reconstruir principal utilitário, Rebuildm.exe. Que tem de reconstruir a base de dados principal para corrigir bases de dados principais está danificadas ou para alterar as definições de agrupamento para a instância. Passos detalhados e informações estão disponíveis no tópico " Como reconstruir a base de dados principal " em SQL Server Books Online. Para além disso, tenha em atenção do problema que é mencionado no seguinte artigo na Microsoft Knowledge Base:
 
Inicie sessão ou registe-se para poder participar.
Back
Topo