Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2000 > SQL Server 2000
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old February 19th, 2005, 10:34 AM
Authorized User
 
Join Date: Feb 2005
Location: Mumbai, Maharashtra, India.
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
Default causes and recovery from suspect mode

can some one tell me that what are the possible causes that mark a database in sql server as suspect mode and how to recover it.

The exact problem is here-

 We're trying to backup the transaction log. as there was not free disk space it failed and the database server has marked as suspected. How to recover it and what is the possible reasons of it.

error log contains mainly following error messages

"BACKUP failed to complete the command BACKUP DATABASE <dbname> TO DISK = N'<Some Path>' WITH NOINIT , NOUNLOAD , NAME = N'BackUp', NOSKIP , STATS = 10, NOFORMAT "

Then it has various occurences of following error message

"The log file for database 'distribution' is full. Back up the transaction log for the database to free up some log space."

"Automatic checkpointing is disabled in database 'distribution' because the log is out of space. It will continue when the database owner successfully checkpoints the database. Free up some space or extend the database and then run the CHECKPOINT statement."

After that lined up with following message repeatedly.

"I/O error (bad page ID) detected during read at offset 0x000000002a2000 in file 'd:\microsoft sql server\mssql\Data\distribution.MDF'.."


Please someone tell me



punkaj
__________________
punkaj
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Suspect database PSilva SQL Server 2000 2 April 13th, 2007 05:44 AM
SQL 2005 Express database mark as 'SUSPECT' dex_bg SQL Server 2005 4 September 19th, 2006 04:07 AM
passowrd recovery Lees ASP.NET 2.0 Professional 2 July 26th, 2006 07:28 AM
Database Suspect Walden SQL Server 2000 1 June 5th, 2003 01:54 AM



All times are GMT -4. The time now is 12:23 PM.


Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.