Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
izaltsman
A custom title
1139 Posts |
Posted - 2001-11-30 : 09:25:48
|
| Hi All! This question actually appeared on SQLTeam a while back, but was never answered:http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=8820Now I have the exact same situation, and I am hoping someone can come up with an explanation. Here is the scoop: I restore my production database regularly on another server. This is a full db restore, I don't need to apply any logs, and hence specify RECOVERY option. Restore process goes OK, but every time I run it, the following message appears in the SQL errorlog:Bypassing recovery for database 'mydb' because it is marked IN LOAD.Yet, when I go to look at the database -- it is fully recovered and operational... Can anyone explain why I am getting this message?SQL7 SP3 |
|
|
RocketScientist
Official SQLTeam Chef
85 Posts |
Posted - 2001-11-30 : 13:34:58
|
| I think it's probably loading the database, and when it completes the load it runs recovery on the database, then it marks the database as no longer IN LOAD and runs recovery again. We get similar logged messages when we attach databases read-only (Bypassing recovery for database 'mydb' because it is marked READ ONLY). |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2001-12-05 : 17:25:47
|
What bothers me, is that this message started appearing in my errorlog just recently even though the job that performs the RESTORE has been around for a long time. I can't think of any changes that I have made recently that would have affected the restore process in any way. So I really don't see why I am getting this message now. The database seems unaffected, but I'm a bit apprehensive when things I can not explain start appearing in the error log. Well, at least it is comforting to know that you are seeing similar messages. |
 |
|
|
|
|
|
|
|