Results 1 to 5 of 5
  1. #1
    Join Date
    May 2003
    Location
    Vancouver, BC, Canada
    Posts
    1

    Unanswered: Help me please! (production DB marked as suspicious)

    Hi everybody,

    DBMS - MS SQL 6.5
    I have removed physical files: Name.DAT and NameLog.DAT
    from folder and put older files there with the same names.
    After restarting the engine has marked my DB as suspicious.

    Then I moved previous files back - database still suspitious!!!

    I have no idea how to restore data base status after removing phisical files?

    I need help as my MS SQL 6.5 marked as suspicious my production
    database.

  2. #2
    Join Date
    Jan 2003
    Location
    China
    Posts
    38
    If you can replace the DB by this way,why MS give some backup,restore function?

  3. #3
    Join Date
    Feb 2003
    Location
    Brisbane, Australia
    Posts
    110

    Re: Help me please! (production DB marked as suspicious)

    If you don't have a valid backup and all you have is the .Dat and .Log files. Try attaching those rather than just replacing the old files. Otherwise have a look at sp_resetstatus.

    Cheers

  4. #4
    Join Date
    Feb 2003
    Location
    Brisbane, Australia
    Posts
    110

    Re: Help me please! (production DB marked as suspicious)

    Sorry, I just noticed that you are on version 6.5. I'm not sure if the info will be valid for that version, you will have to try it to find out.

    Thanks,


    Originally posted by bmalar
    If you don't have a valid backup and all you have is the .Dat and .Log files. Try attaching those rather than just replacing the old files. Otherwise have a look at sp_resetstatus.

    Cheers

  5. #5
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    True you should use SP_RESETSTATUS, before that use:

    sp_configure 'allow updates',1
    go
    reconfigure with override
    go

    After the procedure is created, immediately disable updates to the system tables.
    sp_configure 'allow updates',0
    go

    reconfigure with override
    go

    ... then use SP_RESETSTATUS and reboot the server.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •