The above error message comes up just before SQL Server marks the database as "Suspect" and refuses to open it. Does anyone know what the message means and how to fix it? I think it's a matter of grabbing the backup, but would be nice if it was possible to recover the data.
在SQL Server将数据库标记为“可疑”并拒绝打开它之前,出现上述错误消息。有谁知道这个消息是什么意思以及如何解决它?我认为这是抓住备份的问题,但如果有可能恢复数据会很好。
I've had a look at the kb article but there are no transactions to resolve.
我看过kb文章,但没有要解决的交易。
2 个解决方案
#1
1
It appears that it means your distributed transaction coordinator failed to start correctly when bringing the SQL Server online.
看来这意味着在使SQL Server联机时,分布式事务协调器无法正确启动。
please refer to this ASP.NET forum post and knowledge base article
请参阅这篇ASP.NET论坛帖子和知识库文章
Depending on the level of logging, you should be able to take the last known backup and slowly recover the logs using point in time recovery techniques to slowly bring the database up to the point right before failure began.
根据日志记录的级别,您应该能够使用上次已知的备份并使用时间点恢复技术慢慢恢复日志,以便在故障开始之前将数据库缓慢地提升到该点。
#2
0
run checkdb to find out why it's been marked as suspect and see if it can be recovered without any data loss (win)
运行checkdb以找出它被标记为可疑的原因并查看它是否可以在没有任何数据丢失的情况下恢复(win)
#1
1
It appears that it means your distributed transaction coordinator failed to start correctly when bringing the SQL Server online.
看来这意味着在使SQL Server联机时,分布式事务协调器无法正确启动。
please refer to this ASP.NET forum post and knowledge base article
请参阅这篇ASP.NET论坛帖子和知识库文章
Depending on the level of logging, you should be able to take the last known backup and slowly recover the logs using point in time recovery techniques to slowly bring the database up to the point right before failure began.
根据日志记录的级别,您应该能够使用上次已知的备份并使用时间点恢复技术慢慢恢复日志,以便在故障开始之前将数据库缓慢地提升到该点。
#2
0
run checkdb to find out why it's been marked as suspect and see if it can be recovered without any data loss (win)
运行checkdb以找出它被标记为可疑的原因并查看它是否可以在没有任何数据丢失的情况下恢复(win)