When restoring a database today, restore the database in SSMs with the following code:
RESTORE DATABASE [TEST] from DISK = N ' D:\TEST. BAK ' with FILE = 1,
Move N ' TEST ' to n ' C:\Program Files\Microsoft SQL Server\mssql10_50.mssqlserver\mssql\data\test.mdf ',
Move N ' Test_log ' to n ' C:\Program Files\Microsoft SQL Server\mssql10_50.mssqlserver\mssql\data\test_log. LDF ',
NORECOVERY, nounload, REPLACE, STATS = 10
After the restore succeeds, the database column is refreshed, but it finds an arrow on the test database that is still in the "restore" state, waits a few minutes and remains unchanged, and the database is unusable.
So Niang, find the following Web site:
http://bbs.csdn.net/topics/70037968
There are children's shoes have encountered the same problem, reply to have ZJCXC (Jiangjian) Master's reply, encountered this situation, the following code:
--The following statement is executed in the Query Analyzer, note modify the library name
Restore log your library name with recovery
After executing the above code, the results are as follows:
RESTORE LOG successfully processed 0 pages and took 3.554 seconds (0.000 mb/sec).
The database can then be used as well.
Although it is not clear what the principle is, but the problem is solved.