Search
Subscribe
Categories
- Backup and Restore
- Capacity Planning
- Compression
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- DBCC
- Deadlocks
- Default Trace
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Execution Plan
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Isolation levels
- Jobs
- Latches
- Links
- Locking
- Memory
- Monitor Performance
- MS DTC
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Blocking
- SQL Cachestore
- SQL DAC
- SQL Default Trace
- SQL DTS
- SQL Error Logs
- SQL Execution Plan
- SQL Optimizer
- SQL problems
- SQL Query Tuning
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL Trigger
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- Stored Procedure
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- View
- Virtualization
- Wait Stats
SQLServer-DBA.com Links
Recent Posts
- Forgotten sa password
- Sql server installation is either corrupt or has been tampered with error getting instance id from name
- Find Weak passwords in SQL Server
- Event ID 55 : The file system structure on the disk is corrupt and unusable on volume
- Career in DBA
- Error 3254 – The volume on device BACKUP_PATH is empty
- SQL auto close - Keep it turned off
- Windows Pagefile size for dedicated SQL Servers
- SQL Database Corruption
- max server memory and sql server memory – why is total memory greater than max memory?
14 March,2013 by Jack Vamvas
A DBA reported a database stuck RESTORING status. According to the DBA the restore had finished. On closer inspection the RESTORE command had not included the RECOVERY argument during the RESTORE process
The RECOVERY option sends an instruction to roll back uncommitted transactions. When recovery completes the database switched to ONLINE sql database status
I confirmed the database was in RESTORING database status , and then issued the RESTORE command WITH RECOVERY. :
use master go select * from sys.master_files where db_name(database_id) = 'database_name' GO --extra command to complete restore RESTORE DATABASE database_name WITH RECOVERY
Read More
SQL Database Status with sys.databases
SQL Server Database Status,monitoring and Restores
SQL Server – Difference between restore RECOVERY and NORECOVERY
Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |