Home Forums SQL Server 2005 SQL Server Newbies Restore Transaction Log Error: database not in NORECOVERY/STANDBY mode RE: Restore Transaction Log Error: database not in NORECOVERY/STANDBY mode

  • GilaMonster (2/20/2013)


    Am I correct in saying that the WarehouseDB that you're trying to restore logs to was online and usable before you started? You set the DB to read only (ALTER DATABASE ... SET READ_ONLY...)?

    Server C, where I'm attempting to restore the logs, was actually configured before I came on board. Technically, it is online and usable, but this server is not officially "online in production". Once I can get the transaction logs updating correctly, then we'll turn off Server B and Server C will be operating in a production capacity. I went to WarehouseDB on Server C, did a right click to get to properties, went to Options and then changed the database to Read Only.

    I will follow your suggestion to drop the database and restore a new full backup with STANDBY.

    Correct me if I'm wrong.... Once I get this database restored and do a dry run of restoring the transaction log, I need to do that daily, until Server C is live and in production, right? Obviously if I don't keep this up, then WarehouseDB on Server C will not be in the proper state. For example, if we decide we want to switch to Server C in two weeks I have two choices: 1) do a daily restore of the transaction log on Server C so it is current and ready to go in two weeks or 2) the day of go-live, drop and restore the database to ensure it is current.

    Thank you!!