﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / Data Corruption (SS2K8 / SS2K8 R2)  / restore a db by using OS level database files / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Tue, 21 May 2013 23:51:37 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>Thanks Gila Monster!!</description><pubDate>Thu, 18 Oct 2012 08:05:15 GMT</pubDate><dc:creator>underwoodmf</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>No, you will not be able to use single user mode. You cannot access a database in any way via any means until recovery is complete (or fails).Once more with feeling... check the SQL error log, see how far the recovery is. If it hit the corruption the DB would not be 'in recovery', it would be 'suspect'. You can wait, or you can restore backups. That's pretty much that.</description><pubDate>Thu, 18 Oct 2012 07:54:26 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>There were some "logical fetch" errors (605) showing up in the log before the before the scheduled shutdown. It wasn't able to come up after the recycle.  It's been over 3 days "in recovery". Is it smart to continue waiting? They're not going to let me stretch it out much longer.  If I can't use DAC, will I be able to use sqlcmd to take it to single user and run DBCC?</description><pubDate>Thu, 18 Oct 2012 07:50:33 GMT</pubDate><dc:creator>underwoodmf</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>Nope, you won't be able to access the DB while it's in recovery, at all, DAC or no DAC. How do you know there's corruption? Got the error messages? Or are you just guessing there is some?If you restart SQL, the recovery starts over from the beginning.Wait it out (check the error log for progress reports) or restore from backup.</description><pubDate>Thu, 18 Oct 2012 07:27:11 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>Since my db has been hung "in recovery" for 3 days, would it be wise to try the Dedicated Access Connection and run DBCC to fix corruption?  If so, do I just open DAC from the copmmand line while "in recovery" or do I try to get the database(not the instance) down to single user and then use DAC?  Thanks!!</description><pubDate>Thu, 18 Oct 2012 06:54:30 GMT</pubDate><dc:creator>underwoodmf</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>[quote][b]underwoodmf (10/15/2012)[/b][hr]I'm certain the engine wasn't stopped when the backup ran. Is that a show stopper?[/quote]Quite likely.SQL locks the database files open while it's running. That means that most backup tools will skip the files (they're locked). If you have one of those backup tools that can read locked files then it's a gamble whether those files are usable or not and that's because of the way that SQL writes to the files, they're never guaranteed to be consistent unless the DB is closed, offline, detached or SQL is stopped.Maybe they'll work, maybe they won't.File system backups are not a backup strategy.</description><pubDate>Mon, 15 Oct 2012 12:46:00 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>And when you get it back up and running create a maintenance plan to backup your databases so you can avoid this type of thing in the future.</description><pubDate>Mon, 15 Oct 2012 12:37:59 GMT</pubDate><dc:creator>Sean Lange</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>I'm certain the engine wasn't stopped when the backup ran. Is that a show stopper?</description><pubDate>Mon, 15 Oct 2012 12:30:56 GMT</pubDate><dc:creator>underwoodmf</dc:creator></item><item><title>RE: restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>Maybe. As long as you have both files (log and data) and those copies were taken with the database engine stopped then you should just be able to attach them (take backups of the current files before you do that, with SQL stopped)Are you sure it's hung, not just taking ages to recover (check the error log)?</description><pubDate>Mon, 15 Oct 2012 12:22:13 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>restore a db by using OS level database files</title><link>http://www.sqlservercentral.com/Forums/Topic1372858-2893-1.aspx</link><description>I have '08 instance that has two dbs in it.  No SQL Server backups, only OS level.  One of the dbs started getting the 605 logical fetch error a few days ago.  It's now hung in "in recovery" state.  Can I restore this db simply by shutting the instance down and then restoring the database file(at the OS level) from b4 the errors started?  Then just start the service?</description><pubDate>Mon, 15 Oct 2012 11:46:46 GMT</pubDate><dc:creator>underwoodmf</dc:creator></item></channel></rss>