Bypassing recovery for database

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Jens Kalkbrenner
    #1

    Bypassing recovery for database

    MS SQL-Server 7.0
    Bypassing recovery for database 'EfW_765' because it is marked IN LOAD.
    What does this mean?
    Our customer is backing up is maindatabase and is recovering it to this
    database for testing.
    Our custumer tries it serveral times and then the recovery works and the
    data are corrupt.
    I have written a little programm which does some selects to this database.
    The program is stopped during recovery but our customer beleves that this
    has something to do with our program.
    Error - Office.com
    http://support.microsoft.com/default.aspx?scid=kb;en-us;272683

    This article doesnt halp me much. So hwat is the meaning of IN LOAD and what
    does the server do if it bypasses the recovery.

    THX

    Jens


    Tags: None
    • Simon Hayes
      #2
      Re: Bypassing recovery for database


      "Jens Kalkbrenner" <jens.kalkbrenn er@wsk.de> wrote in message
      news:c5gccs$73a $01$1@news.t-online.com...[color=blue]
      > MS SQL-Server 7.0
      > Bypassing recovery for database 'EfW_765' because it is marked IN LOAD.
      > What does this mean?
      > Our customer is backing up is maindatabase and is recovering it to this
      > database for testing.
      > Our custumer tries it serveral times and then the recovery works and the
      > data are corrupt.
      > I have written a little programm which does some selects to this database.
      > The program is stopped during recovery but our customer beleves that this
      > has something to do with our program.
      > http://support.microsoft.com/default...b;en-us;272683
      > This article doesnt halp me much. So hwat is the meaning of IN LOAD and[/color]
      what[color=blue]
      > does the server do if it bypasses the recovery.
      >
      > THX
      >
      > Jens
      >
      >[/color]

      I'm not entirely sure, but it sounds as if the database has been partially
      recovered, and then the MSSQLServer service has been restarted. This might
      be normal, if someone is recovering the database by applying mutiple log
      files, for example. Have you tried this, to restore the database and make it
      available?

      RESTORE DATABASE EfW_765 FROM ... WITH RECOVERY

      If this doesn't help, can you give some more details about exactly what is
      happening? Is the recovery from a full backup only or from a full backup
      plus logfiles? What do you mean when you say the data is "corrupt"? Are you
      sure you're recovering the correct backup set? Is the customer trying to
      copy database A to database B using backup/restore? If so, have you followed
      the steps in Books Online under "Copying Databases"?

      Simon


        Comment

        • Simon Hayes
          #3
          Re: Bypassing recovery for database


          "Jens Kalkbrenner" <jens.kalkbrenn er@wsk.de> wrote in message
          news:c5gccs$73a $01$1@news.t-online.com...[color=blue]
          > MS SQL-Server 7.0
          > Bypassing recovery for database 'EfW_765' because it is marked IN LOAD.
          > What does this mean?
          > Our customer is backing up is maindatabase and is recovering it to this
          > database for testing.
          > Our custumer tries it serveral times and then the recovery works and the
          > data are corrupt.
          > I have written a little programm which does some selects to this database.
          > The program is stopped during recovery but our customer beleves that this
          > has something to do with our program.
          > http://support.microsoft.com/default...b;en-us;272683
          > This article doesnt halp me much. So hwat is the meaning of IN LOAD and[/color]
          what[color=blue]
          > does the server do if it bypasses the recovery.
          >
          > THX
          >
          > Jens
          >
          >[/color]

          I'm not entirely sure, but it sounds as if the database has been partially
          recovered, and then the MSSQLServer service has been restarted. This might
          be normal, if someone is recovering the database by applying mutiple log
          files, for example. Have you tried this, to restore the database and make it
          available?

          RESTORE DATABASE EfW_765 FROM ... WITH RECOVERY

          If this doesn't help, can you give some more details about exactly what is
          happening? Is the recovery from a full backup only or from a full backup
          plus logfiles? What do you mean when you say the data is "corrupt"? Are you
          sure you're recovering the correct backup set? Is the customer trying to
          copy database A to database B using backup/restore? If so, have you followed
          the steps in Books Online under "Copying Databases"?

          Simon


            Comment

            Previous template Next
            Working...