<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
Data Corruption
»
Attach Database failed for server 'M3'
13 posts, Page 1 of 2
1
2
»»
Attach Database failed for server 'M3'
Rate Topic
Display Mode
Topic Options
Author
Message
deba_20032004
deba_20032004
Posted Saturday, May 26, 2012 5:12 AM
Valued Member
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:33 AM
Points: 50,
Visits: 219
Dear Sir,
I am in great trouble, at present I have no back of the database, while i attaching database in the sql server 2000, the Sql server giving error message which was mentioned below within single quotes.
'Attach database failed for Server 'M3'. (Microsoft.SqlServer.Smo)
An exception occurred while executing a Transact-SQL statement or batch.
I/O error (torn page) detected during read at offset 0x0000003d0f4000 in file 'D:\TEST\DS1213.mdf'.
Error while redoing logged operation in database 'DS1213'. Error at log record ID (1081:4550:10).
Could not open new database 'DS1213'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 823)'
how to attach the database I don't know please help me anybody
Thanking You
Debasis Bag
Post #1306941
GilaMonster
GilaMonster
Posted Saturday, May 26, 2012 5:19 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 3:18 PM
Points: 37,744,
Visits: 30,025
No backup? Seriously why the hell not?
Your database is corrupt, it may be possible to get it back with some data loss, it may not. You need to 'hack' the database back into SQL Server.
Copy those files somewhere safe for the moment.
Create a new database with the same file structure (same number of files, same logical names) as the files for the DB you can't attach.
Stop SQL Server
Delete the files for the newly created database and put the files from that damaged database in their place.
Restart SQL Server. The database will probably come up suspect.
Once you're that far, post the error log entries and the output of querying sysdatabases for that DB. DO NOTHING ELSE AT THIS POINT.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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
Post #1306942
GilaMonster
GilaMonster
Posted Saturday, May 26, 2012 8:05 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 3:18 PM
Points: 37,744,
Visits: 30,025
Please post the outcomes and messages here, not elsewhere. Keeping things in one place makes problems far easier to solve.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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
Post #1306968
seven.srikanth
seven.srikanth
Posted Saturday, May 26, 2012 8:26 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, May 09, 2013 8:29 AM
Points: 33,
Visits: 373
Try attaching to Higher Version of SQL server, if attaching works fix it. detach it and attach it back to SQL Server 2000.
I'm not sure, that this will work. But worth giving a try.
Post #1306970
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Saturday, May 26, 2012 8:30 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 11:20 AM
Points: 31,437,
Visits: 13,752
Try attaching to Higher Version of SQL server, if attaching works fix it. detach it and attach it back to SQL Server 2000.
That will not work. Once you attach to a higher version, you cannot ever attach it back to a lower one.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1306972
seven.srikanth
seven.srikanth
Posted Saturday, May 26, 2012 8:33 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, May 09, 2013 8:29 AM
Points: 33,
Visits: 373
I haven't done that before..
I'm aware that backups can't be restored to lower version and not about this.
Thanks for your inputs...
Post #1306973
GilaMonster
GilaMonster
Posted Saturday, May 26, 2012 8:33 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 3:18 PM
Points: 37,744,
Visits: 30,025
seven.srikanth (5/26/2012)
Try attaching to Higher Version of SQL server, if attaching works fix it. detach it and attach it back to SQL Server 2000.
I'm not sure, that this will work. But worth giving a try.
Not only won't it work, but it's far less likely that a damaged database will attach to a higher version than to the version it was detached from and if it does by some small miracle work, the OP would not be able to get the DB back to the lower version.
Please don't give advice in the data corruption forums that can make a situation worse.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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
Post #1306974
prettsons
prettsons
Posted Wednesday, May 30, 2012 2:03 AM
SSC Journeyman
Group: General Forum Members
Last Login: 2 days ago @ 11:45 PM
Points: 99,
Visits: 1,036
The I/O error (torn page) error occurs when SQL Server tried to access a page that had previously not been written to disk correctly. This can be happen due to power failure, disk failure, hardware failure when the disk is being written to.
When this error occurs, sql server ended your connection. If the torn page was detected during database recovery, then SQL Server will mark it as SUSPECT.
Solution:
First Check your error logs and then restore your database form last good backups and transaction logs. It will definitely fix the problem, but you should also check your disk and fix any issues if there was a disk hardware failure. You can also use third party sql database recovery software to resolve this error.
SQL Database Recovery Expert
Post #1308146
Schadenfreude-Mei
Schadenfreude-Mei
Posted Wednesday, May 30, 2012 3:08 AM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, March 21, 2013 8:40 AM
Points: 1,099,
Visits: 1,320
prettsons (5/30/2012)
The I/O error (torn page) error occurs when SQL Server tried to access a page that had previously not been written to disk correctly. This can be happen due to power failure, disk failure, hardware failure when the disk is being written to.
When this error occurs, sql server ended your connection. If the torn page was detected during database recovery, then SQL Server will mark it as SUSPECT.
Solution:
First Check your error logs and then restore your database form last good backups and transaction logs. It will definitely fix the problem, but you should also check your disk and fix any issues if there was a disk hardware failure. You can also use third party sql database recovery software to resolve this error.
The OP has said that there are no backups :-(
Adam Zacks
-------------------------------------------
Be Nice, Or Leave
Post #1308182
prettsons
prettsons
Posted Wednesday, May 30, 2012 3:24 AM
SSC Journeyman
Group: General Forum Members
Last Login: 2 days ago @ 11:45 PM
Points: 99,
Visits: 1,036
Schadenfreude-Mei (5/30/2012)
prettsons (5/30/2012)
The I/O error (torn page) error occurs when SQL Server tried to access a page that had previously not been written to disk correctly. This can be happen due to power failure, disk failure, hardware failure when the disk is being written to.
When this error occurs, sql server ended your connection. If the torn page was detected during database recovery, then SQL Server will mark it as SUSPECT.
Solution:
First Check your error logs and then restore your database form last good backups and transaction logs. It will definitely fix the problem, but you should also check your disk and fix any issues if there was a disk hardware failure. You can also use third party sql database recovery software to resolve this error.
The OP has said that there are no backups :-(
I shall suggest to Debasis Bag to try third party sql database recovery software.
SQL Database Recovery Expert
Post #1308189
« Prev Topic
|
Next Topic »
13 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
