SQL Server Performance

Windows Rebuild-->DB suspect issue

Discussion in 'General DBA Questions' started by akothand, Jun 3, 2006.

  1. akothand New Member

    Now, this is a strange combination of events:<br /><br />1. Database A is publisher in the server X. Datafile is on G: and Logfile on H:. <br />2. Server X gets rebuilt and master database gets restored fine.<br />3. Voila...there is no H: drive. The build team does not restore the driver letters <br /> proper. H: drive is now named E: drive and some low capacity partition becomes H: <br /> (system drive)<br />4. Our master database still thinks database A's logfile is on H: drive. So, it is <br /> stamped "Suspect". We cannot move this logfile to H: drive now, as there is no space <br /> on that drive.<br />5. This database A cannot be detached or taken offline as it is part of <br /> replication. But, replication cannot be disabled as SQL server cannot access database <br /> A. Vicious circle !<img src='/community/emoticons/emotion-1.gif' alt=':)' /><br /><br />so what do you think my peers? let me know your opinion if there is a way to change the logfile path in the master database.<br /><br />Thanks for your time<br /> <br /><br /><br />Thanks,<br />Anand.K<br /><br />Purity, patience, and perseverance are the three essentials to success<br />and, above all, love - Swami Vivekananda
  2. satya Moderator

    This is one of the best example to work out with System Admins in order to maintain & manage similar setup when there is a disaster recovery.<br /><br />I hope you will have a final backup for that database 'A' (in good condition [<img src='/community/emoticons/emotion-1.gif' alt=':)' />].<br />Run DROP DATABASE to drop that suspect database and then RESTORE that database using WITH MOVE Option in order to identify the new home (drives) as per your setup.<br /><br />Refer to the Books online for more information on RESTORE ..WITH MOVE option information.<br /><br /><br /><hr noshade size="1"><b>Satya SKJ</b><br />Microsoft SQL Server MVP<br />Contributing Editor & Forums Moderator<br /<a target="_blank" href=http://www.SQL-Server-Performance.Com>http://www.SQL-Server-Performance.Com</a><br /><center><font color="teal"><font size="1">This posting is provided �AS IS� with no rights for the sake of <i>knowledge sharing.</i></font id="size1"></font id="teal"></center>
  3. akothand New Member

    <img src='/community/emoticons/emotion-1.gif' alt=':)' /> yeah..it was very frustrating when i saw the error log and knew what happened.<br /><br />Thanks Satya. I had done that over the weekend. <br />Now i know for sure there is no way you can change the master log file path to trick the server <img src='/community/emoticons/emotion-1.gif' alt=':)' /><br /><br /><br /><br /><br /><br />Thanks,<br />Anand.K<br /><br />Purity, patience, and perseverance are the three essentials to success<br />and, above all, love - Swami Vivekananda
  4. satya Moderator

    No you can, once the database is dropped the values will be wiped from master (SQL) database and again you can re-attach or restore with new location what I've suggested above.

    Satya SKJ
    Microsoft SQL Server MVP
    Contributing Editor & Forums Moderator
    This posting is provided �AS IS� with no rights for the sake of knowledge sharing.
  5. akothand New Member

    the irony is database will not get dropped, as it is used for replication..
    Replication cannot be dropped as the database itself is inaccessible..
    So, it is still hanging in "suspect" mode


    Purity, patience, and perseverance are the three essentials to success
    and, above all, love - Swami Vivekananda

Share This Page