enrique_aeo
asked on
sql dumper - many
hello
I have reviewed the server and I find several SqlDumper processes associated with a failure in the SQLServer. This process arises when the service DB or damaged. Previously not shown these processes.
what can i do?
sqlDUMPER.png
I have reviewed the server and I find several SqlDumper processes associated with a failure in the SQLServer. This process arises when the service DB or damaged. Previously not shown these processes.
what can i do?
sqlDUMPER.png
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The SPN error again? :)
I wrote an article about that error. Check if it helps you.
I wrote an article about that error. Check if it helps you.
ASKER
Please, could you review the entire file ERRORLOG.
Those databases weren't the ones that was marked as suspect from your another question day ago?
I would run a DBCC CHECKDB on them.
I would run a DBCC CHECKDB on them.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If you run the DBCC CHECKDB and showed error: can not because the database is in suspect mode
So, it's confirmed that are those databases in suspect mode. You can't do nothing until resolve that issue. That's why SQL Server is dumping all the time.
ASKER
then I must reinstall the SQL server?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
it is too many error
2015-07-16 09:13:10.74 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x200b, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
ERRORLOG