SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


A guide to recover a database out from Suspect mode


A guide to recover a database out from Suspect mode

Author
Message
GilaMonster
GilaMonster
SSC Guru
SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)

Group: General Forum Members
Points: 221592 Visits: 46281
y.koteswarrao-652921 (2/9/2010)
This is artice is very good and usefull in solving


No, the article is neither good nor useful. Read over the prior comments to see why.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


DMarvez
DMarvez
Old Hand
Old Hand (309 reputation)Old Hand (309 reputation)Old Hand (309 reputation)Old Hand (309 reputation)Old Hand (309 reputation)Old Hand (309 reputation)Old Hand (309 reputation)Old Hand (309 reputation)

Group: General Forum Members
Points: 309 Visits: 313
Hi Gail,

I suspect he\she was commenting on the followup comments regarding corruption, dbcc, video links etc..

Thanks to everyone for posting the links and other comments, it turned a bad article into a great resource for others.

Dave
Vee
Vee
SSC Eights!
SSC Eights! (941 reputation)SSC Eights! (941 reputation)SSC Eights! (941 reputation)SSC Eights! (941 reputation)SSC Eights! (941 reputation)SSC Eights! (941 reputation)SSC Eights! (941 reputation)SSC Eights! (941 reputation)

Group: General Forum Members
Points: 941 Visits: 421
i believe it should be
RESTORE DATABASE <suspecteddatabasename> WITH RECOVERY
GilaMonster
GilaMonster
SSC Guru
SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)SSC Guru (221K reputation)

Group: General Forum Members
Points: 221592 Visits: 46281
Vee (2/10/2010)
i believe it should be
RESTORE DATABASE <suspecteddatabasename> WITH RECOVERY


Yes, however that does not fix a suspect database. It brings a database that's in the RESTORING... state Online.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Rolando Hernandez
Rolando Hernandez
Valued Member
Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)

Group: General Forum Members
Points: 64 Visits: 72
Very nice article.

I remember one of my production databases went to SUSPECT, basically the drive where the data/log files were located ran out of space.

Basically I released space, stopped-started the sql service and voilá. The database came online.

Rolando.
TravisDBA
TravisDBA
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3308 Visits: 3069
BTW, you can write some T-SQL code with little effort that will check disk space on all fixed drives on your db server via a daily job and notify you via email if available space on any of your drives falls below a given amount. This is indispensable in preventing this from catching you unaware and sending your database into suspect mode before you can do something about it Smile Let me know through email talltop@bellsouth.net if you are interested and I can send it to you....

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
M&M
M&M
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6003 Visits: 3913
TravisDBA (2/10/2010)
BTW, you can write some T-SQL code with little effort that will check disk space on all fixed drives on your db server via a daily job and notify you via email if available space on any of your drives falls below a given amount. This is indispensable in preventing this from catching you unaware and sending your database into suspect mode before you can do something about it Smile Let me know through email talltop@bellsouth.net if you are interested and I can send it to you....


Travis, Thanks for your points.

Do you have any suggestions if we need to use this script for around 200 to 250 instances.

Then we would need to use SQLCMD or ISQL right? That is to connect to each one of them. However, ISQL would no longer be supported in future.

Otherwise, it would get too manual to set 250 jobs for 250 servers to monitor disk space.

M&M
Malcolm Daughtree
Malcolm Daughtree
Mr or Mrs. 500
Mr or Mrs. 500 (557 reputation)Mr or Mrs. 500 (557 reputation)Mr or Mrs. 500 (557 reputation)Mr or Mrs. 500 (557 reputation)Mr or Mrs. 500 (557 reputation)Mr or Mrs. 500 (557 reputation)Mr or Mrs. 500 (557 reputation)Mr or Mrs. 500 (557 reputation)

Group: General Forum Members
Points: 557 Visits: 335
The more I read on this thread the more worried I become... do you actually believe this ...?

RUNNING OUT OF DISK SPACE WILL NOT SEND YOUR DATABASES SUSPECT.

Come on guys read Books on line, buy an Admin guide, heck fill a disk drive and see what happens. Thankfully its comments like these that keep employers worried and me employeed.
Paul Randal
Paul Randal
SSCrazy Eights
SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)

Group: General Forum Members
Points: 8096 Visits: 1719
I heard this anecdotally several times while writing CHECKDB and emergency mode repair for 2005. Spent several days trying to force SQL Server to make a database go suspect because of running out of space.

It's not possible in 2000 onwards. The transaction log reserves space in itself to guarantee that in-flight transactions can always rollback and not make the database go suspect. Hitting a corrupt page during a rollback will make the database go suspect however. Running out of space cannot, unless rollback hits a corrupt page (that it didn't hit during the actual transaction). That's corruption - that's not running out of space.

Thanks

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Rolando Hernandez
Rolando Hernandez
Valued Member
Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)

Group: General Forum Members
Points: 64 Visits: 72
I know the SQL is prepared for every known bad situation, but it still fails.

I've seen lot of situations where the package should not fail and it does. Here is another story about space : A DBCC that hungs or stalls because there is not enough space on disk. Error log reports "...waiting for FCB_Replica...".

The database is 150GB and the free space is about 70GB. When I released some to some 120 GB, it runs smootly.

I've read many msdn blogs, articles, none realy gave a real solution, releasing space gave it.

Well this comment is out of the topic but this confirms that all sistems fails. I still like the package and is very reliable but I'm confident that all systems fails sometimes with unexpected issues.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search