Microsoft SQL Database that was in Recovery Pending mode
Fundamentally , this error is closely correlated to that Forcibly deletion process of File stream file which I do think no other solution except waiting to finish recovery mode and either wise it will end with :
The most optimistic probability that it will end up with Online mode …So it will be fine and no need for any further action ( Just you have to wait for a longer time if log file was such huge)..
The most pessimistic probability that it will end up with suspect mode ..SO it will be need to run the below process of DB Repair but bear in mind that data loss might be there;
Stop SQL Server and remove transaction log file of this DB then restart again where DB should go with suspect mode ….If so you can run the below query
ALTER DATABASE [DB_Name] SET SINGLE_USER WITH NO_WAIT
ALTER DATABASE [DB_Name] SET EMERGENCY;
DBCC checkdb ([DB_Name], REPAIR_ALLOW_DATA_LOSS )
ALTER DATABASE [DB_Name] SET online;
ALTER DATABASE [DB_Name] SET Multi_USER WITH NO_WAIT
Fundamentally , this error is closely correlated to that Forcibly deletion process of File stream file which I do think no other solution except waiting to finish recovery mode and either wise it will end with :
The most optimistic probability that it will end up with Online mode …So it will be fine and no need for any further action ( Just you have to wait for a longer time if log file was such huge)..
The most pessimistic probability that it will end up with suspect mode ..SO it will be need to run the below process of DB Repair but bear in mind that data loss might be there;
Stop SQL Server and remove transaction log file of this DB then restart again where DB should go with suspect mode ….If so you can run the below query
ALTER DATABASE [DB_Name] SET SINGLE_USER WITH NO_WAIT
ALTER DATABASE [DB_Name] SET EMERGENCY;
DBCC checkdb ([DB_Name], REPAIR_ALLOW_DATA_LOSS )
ALTER DATABASE [DB_Name] SET online;
ALTER DATABASE [DB_Name] SET Multi_USER WITH NO_WAIT
No comments:
Post a Comment