Results 1 to 2 of 2

Thread: suspec model

  1. #1
    Join Date
    Dec 2003
    Posts
    14

    Unanswered: suspec model

    I moved the devices to different physical location and edited the device location in sysdatabases. the problem was I had to start the server to make the changes, which I did. however, master did not find some devices and marked the DB as suspect. One of the is model (status 320). I brought server in a single user mode but won't let me clear the suspect flag and won't let me drop the db "dbcc dbrepair(dbname,dropdb)"since it is a system DB.

    Any help will be greatly appreciated

  2. #2
    Join Date
    Jan 2004
    Posts
    545
    Provided Answers: 4

    Post

    Editting the systables always brings some risks along.
    To move devices, you can use device-mirroring.

    Enable device-mirroring using sp_configure "disable disk mirroring", 0 (requires a restart of ASE).
    Make a mirror of the device using
    Code:
    disk mirror 
         name = "device_name" , 
         mirror = "physicalname" 
         [, writes = { serial | noserial }]
    Then, when the device is mirrored, unmirror the device with
    Code:
    disk unmirror 
         name = "device_name" 
         [ ,side = { "primary" | secondary }] 
         [ ,mode = { retain | remove }]
    Disable the primary side, leaving the secondary side as the new devicelocation.

Posting Permissions

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