• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 884
  • Last Modified:

SQL database

Need some help does anyone knows how i can recover a mdf file.  I have a few databases but one of them give me error when i want to attatch to SQL. I have the MDF e LDF files but need help to detect and correct those erros in a way that i can attatch without problems.
0
naptor
Asked:
naptor
  • 8
  • 7
1 Solution
 
bull_riderCommented:
Before follwing these steps please take a backup of thh existing mdf and ldf files.1. Create a new database with same MDF and LDF name2. Stop sql server and delete the new MDF file and copy the old MDF file3. Start SQL Server and verify the status of the database. If the database status is suspect do the following scripts in Query Analyzer:
a. Override updates in Master Table

    Use Master
    Go
    sp_configure 'allow updates', 1
    reconfigure with override
    Go

b. Get the value of the status column in sysdatabases table

    select * from sysdatabases where name = 'db_name'
    -- note the value of the status column for later use in # f
    begin tran

c. Set status of the database to suspect (32768)

    update sysdatabases set status = 32768 where name ='db_name'
    commit tran

d. Rebuild transaction log

    DBCC rebuild_log('db_name','db_log_path')

e. Set the database to single user access

    sp_dboption '', 'single user', 'true'
    DBCC checkdb('db_name')
    Go

f. Restore the status of the database in sysdatabases table

    begin tran
    update sysdatabases set status = previous_value where name = 'db_name'


    -- verify one row is updated before committing
    commit tran
    Go

g. Restore the override property of Master table

    sp_configure 'allow updates', 0
    reconfigure with override
    Go

4. Now open or refresh the enterprise manager you can now see the tables inside the fixed database.

If any problems still persist, you can import all tables into temporary database and drop the original database. Create a new database with same name then re-import all the tables from the temporary database.

Hope this solves your issue. :)
0
 
naptorAuthor Commented:
i tryied to do the process but on line b got this error " Server: Msg 207, Level 16, State 3, Line 1
Invalid column name 'MARPINO'. "

Help needed
0
 
bull_riderCommented:
Can you tell me on which step you encountered this error? or which statement gave this error?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
naptorAuthor Commented:
this error is on statement b. Get the value of the status column in sysdatabases table

   select * from sysdatabases where name = 'db_name'
   -- note the value of the status column for later use in # f
   begin tran
0
 
bull_riderCommented:
I think you are executing the it without single quotes

Try this:

select * from sysdatabases where name = 'MARPINO'
0
 
bull_riderCommented:
And that too that should be run under master database
0
 
naptorAuthor Commented:
now i have a problem in - e. Set the database to single user access

   sp_dboption '', 'single user', 'true'
   DBCC checkdb('db_name')
   Go
 error

Server: Msg 15010, Level 16, State 1, Procedure sp_dboption, Line 71
The database '' does not exist. Use sp_helpdb to show available databases.
0
 
bull_riderCommented:
Oops my mistake that should be :

sp_dboption 'MARPINO', 'single user', 'true'
   DBCC checkdb('MARPINO')
   Go

0
 
naptorAuthor Commented:
after that error

Server: Msg 945, Level 14, State 2, Line 1
Database 'MARPINO' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
Server: Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
sp_dboption command failed.
Server: Msg 945, Level 14, State 2, Line 2
Database 'MARPINO' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
0
 
bull_riderCommented:
2. Stop sql server and delete the new MDF file and copy the old MDF file

In this step did you copy the old LDF file as well. If not please do so and then try. I forgot to add teh LDF thing there. I apologize.
0
 
naptorAuthor Commented:
error after

Server: Msg 926, Level 14, State 1, Line 1
Database 'MARPINO' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Server: Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
sp_dboption command failed.
Server: Msg 926, Level 10, State 1, Line 2
Database 'MARPINO' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
0
 
bull_riderCommented:
Please follow the steps to recover a suspect database
EXEC sp_resetstatus 'MARPINO'
ALTER DATABASE MARPINO SET EMERGENCY
DBCC checkdb('MARPINO')
ALTER DATABASE MARPINO SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB ('MARPINO', REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE MARPINO SET MULTI_USER

Open in new window

0
 
bull_riderCommented:
Did this issue get resolved? If so could you please mark it as answered?
0
 
naptorAuthor Commented:
bull_rider    

thanks for the supplied support but i think the log file as errors and a friend recovered the database
0
 
naptorAuthor Commented:
for the quick help given to this question  thanks
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now