|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Marked "IN LOAD" messages
I do restores on a daily basis. The restores are taken from DISK backups. I
am not using backup devices. I am noticing all these errors in the log file: Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. When I do the restore, I am using the gui (rt click on database, select restore). Sometimes I need to restore over an existing DB, other times I restore to a new database. Any ideas? I want to make sure I am doing the restores correctly and remove these errors Is it possible if I do not specify "Force over existing Database" that it can
cause this error? Show quoteHide quote "Kristen" wrote: > I do restores on a daily basis. The restores are taken from DISK backups. I > am not using backup devices. > I am noticing all these errors in the log file: > Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. > When I do the restore, I am using the gui (rt click on database, select > restore). > Sometimes I need to restore over an existing DB, other times I restore to a > new database. > Any ideas? I want to make sure I am doing the restores correctly and remove > these errors Try using the 'WITH RECOVERY' OPTION and issue the restore command via TSQL
and not the Gui. Show quoteHide quote "Kristen" <Kris***@discussions.microsoft.com> wrote in message news:9FE4EEAE-6332-4F67-BA23-6D1AA00878D3@microsoft.com... > Is it possible if I do not specify "Force over existing Database" that it > can > cause this error? > > "Kristen" wrote: > >> I do restores on a daily basis. The restores are taken from DISK >> backups. I >> am not using backup devices. >> I am noticing all these errors in the log file: >> Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. >> When I do the restore, I am using the gui (rt click on database, select >> restore). >> Sometimes I need to restore over an existing DB, other times I restore to >> a >> new database. >> Any ideas? I want to make sure I am doing the restores correctly and >> remove >> these errors I tried doing it in TSQL........didn't work
RESTORE DATABASE test2 FROM DISK = 'E:\MSSQL\Backup\LVTS_Min_03122007.bak' WITH RECOVERY, MOVE 'LVTS_Min_Data' TO 'E:\MSSQL\Backup\test2_data.mdf', MOVE 'LVTS_Min_Log' TO 'E:\MSSQL\Backup\test2_log.ldf' Bypassing recovery for database 'test2' because it is marked IN LOAD. Starting up database 'test2'. Recovery is checkpointing database 'test2' (58) Show quoteHide quote "Immy" wrote: > Try using the 'WITH RECOVERY' OPTION and issue the restore command via TSQL > and not the Gui. > > "Kristen" <Kris***@discussions.microsoft.com> wrote in message > news:9FE4EEAE-6332-4F67-BA23-6D1AA00878D3@microsoft.com... > > Is it possible if I do not specify "Force over existing Database" that it > > can > > cause this error? > > > > "Kristen" wrote: > > > >> I do restores on a daily basis. The restores are taken from DISK > >> backups. I > >> am not using backup devices. > >> I am noticing all these errors in the log file: > >> Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. > >> When I do the restore, I am using the gui (rt click on database, select > >> restore). > >> Sometimes I need to restore over an existing DB, other times I restore to > >> a > >> new database. > >> Any ideas? I want to make sure I am doing the restores correctly and > >> remove > >> these errors > > > So - to clarify, you did a full backup of your database, then copy the
database to a new location and then restore it? What happens if you restore the backup on the same server that the backup was taken from? Show quoteHide quote "Kristen" <Kris***@discussions.microsoft.com> wrote in message news:5365DC0E-0F94-4109-A028-E775E00E8A10@microsoft.com... >I tried doing it in TSQL........didn't work > > RESTORE DATABASE test2 > FROM DISK = 'E:\MSSQL\Backup\LVTS_Min_03122007.bak' > WITH RECOVERY, > MOVE 'LVTS_Min_Data' TO 'E:\MSSQL\Backup\test2_data.mdf', > MOVE 'LVTS_Min_Log' TO 'E:\MSSQL\Backup\test2_log.ldf' > > Bypassing recovery for database 'test2' because it is marked IN LOAD. > Starting up database 'test2'. > Recovery is checkpointing database 'test2' (58) > > > "Immy" wrote: > >> Try using the 'WITH RECOVERY' OPTION and issue the restore command via >> TSQL >> and not the Gui. >> >> "Kristen" <Kris***@discussions.microsoft.com> wrote in message >> news:9FE4EEAE-6332-4F67-BA23-6D1AA00878D3@microsoft.com... >> > Is it possible if I do not specify "Force over existing Database" that >> > it >> > can >> > cause this error? >> > >> > "Kristen" wrote: >> > >> >> I do restores on a daily basis. The restores are taken from DISK >> >> backups. I >> >> am not using backup devices. >> >> I am noticing all these errors in the log file: >> >> Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. >> >> When I do the restore, I am using the gui (rt click on database, >> >> select >> >> restore). >> >> Sometimes I need to restore over an existing DB, other times I restore >> >> to >> >> a >> >> new database. >> >> Any ideas? I want to make sure I am doing the restores correctly and >> >> remove >> >> these errors >> >> >> For this test, I took a backup, then restored it to a new database. When I
did that I got the error. I am only working with 1 server so I did restore the backup on the same server that the backup was taken from. #2 - Most of the time, I need to restore a backup (from another DB) to an existing database. I was using the GUI for this also. I think that may be why I am having these messages in the log. Can you give me an idea for the #2 scenario above what my RESTORE DATABASE options should be? Thanks for your help with this. Show quoteHide quote "Immy" wrote: > So - to clarify, you did a full backup of your database, then copy the > database to a new location and then restore it? > What happens if you restore the backup on the same server that the backup > was taken from? > > > "Kristen" <Kris***@discussions.microsoft.com> wrote in message > news:5365DC0E-0F94-4109-A028-E775E00E8A10@microsoft.com... > >I tried doing it in TSQL........didn't work > > > > RESTORE DATABASE test2 > > FROM DISK = 'E:\MSSQL\Backup\LVTS_Min_03122007.bak' > > WITH RECOVERY, > > MOVE 'LVTS_Min_Data' TO 'E:\MSSQL\Backup\test2_data.mdf', > > MOVE 'LVTS_Min_Log' TO 'E:\MSSQL\Backup\test2_log.ldf' > > > > Bypassing recovery for database 'test2' because it is marked IN LOAD. > > Starting up database 'test2'. > > Recovery is checkpointing database 'test2' (58) > > > > > > "Immy" wrote: > > > >> Try using the 'WITH RECOVERY' OPTION and issue the restore command via > >> TSQL > >> and not the Gui. > >> > >> "Kristen" <Kris***@discussions.microsoft.com> wrote in message > >> news:9FE4EEAE-6332-4F67-BA23-6D1AA00878D3@microsoft.com... > >> > Is it possible if I do not specify "Force over existing Database" that > >> > it > >> > can > >> > cause this error? > >> > > >> > "Kristen" wrote: > >> > > >> >> I do restores on a daily basis. The restores are taken from DISK > >> >> backups. I > >> >> am not using backup devices. > >> >> I am noticing all these errors in the log file: > >> >> Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. > >> >> When I do the restore, I am using the gui (rt click on database, > >> >> select > >> >> restore). > >> >> Sometimes I need to restore over an existing DB, other times I restore > >> >> to > >> >> a > >> >> new database. > >> >> Any ideas? I want to make sure I am doing the restores correctly and > >> >> remove > >> >> these errors > >> > >> > >> > > > "Kristen" <Kris***@discussions.microsoft.com> wrote in message Why do you think these are "errors"? The sql server log file contains news:5365DC0E-0F94-4109-A028-E775E00E8A10@microsoft.com... >I tried doing it in TSQL........didn't work > > RESTORE DATABASE test2 > FROM DISK = 'E:\MSSQL\Backup\LVTS_Min_03122007.bak' > WITH RECOVERY, > MOVE 'LVTS_Min_Data' TO 'E:\MSSQL\Backup\test2_data.mdf', > MOVE 'LVTS_Min_Log' TO 'E:\MSSQL\Backup\test2_log.ldf' > > Bypassing recovery for database 'test2' because it is marked IN LOAD. > Starting up database 'test2'. > Recovery is checkpointing database 'test2' (58) messages, some of which may be errors but many of which are not. The messages you see are standard messages that indicate a successful restore (btw - I don't think you posted all the relevant messages since there should be a "Database restored: Database: <dbname>, creation ..." message. I want to make sure the "IN LOAD" messages that I am getting will not create
any issues in the future. Do you know of any potential problems I could face when getting this "IN LOAD" message Show quoteHide quote "Scott Morris" wrote: > "Kristen" <Kris***@discussions.microsoft.com> wrote in message > news:5365DC0E-0F94-4109-A028-E775E00E8A10@microsoft.com... > >I tried doing it in TSQL........didn't work > > > > RESTORE DATABASE test2 > > FROM DISK = 'E:\MSSQL\Backup\LVTS_Min_03122007.bak' > > WITH RECOVERY, > > MOVE 'LVTS_Min_Data' TO 'E:\MSSQL\Backup\test2_data.mdf', > > MOVE 'LVTS_Min_Log' TO 'E:\MSSQL\Backup\test2_log.ldf' > > > > Bypassing recovery for database 'test2' because it is marked IN LOAD. > > Starting up database 'test2'. > > Recovery is checkpointing database 'test2' (58) > > Why do you think these are "errors"? The sql server log file contains > messages, some of which may be errors but many of which are not. The > messages you see are standard messages that indicate a successful restore > (btw - I don't think you posted all the relevant messages since there should > be a "Database restored: Database: <dbname>, creation ..." message. > > > No I didn't post all the messages. The database did successfully restore. I
want to understand what I am doing wrong when restoring these databases so the messages are not written to the log. Most of the time I am taking a backup of 1 database and restoring it to another existing DB. Using the GUI for the restore. Any ideas? Show quoteHide quote "Scott Morris" wrote: > "Kristen" <Kris***@discussions.microsoft.com> wrote in message > news:5365DC0E-0F94-4109-A028-E775E00E8A10@microsoft.com... > >I tried doing it in TSQL........didn't work > > > > RESTORE DATABASE test2 > > FROM DISK = 'E:\MSSQL\Backup\LVTS_Min_03122007.bak' > > WITH RECOVERY, > > MOVE 'LVTS_Min_Data' TO 'E:\MSSQL\Backup\test2_data.mdf', > > MOVE 'LVTS_Min_Log' TO 'E:\MSSQL\Backup\test2_log.ldf' > > > > Bypassing recovery for database 'test2' because it is marked IN LOAD. > > Starting up database 'test2'. > > Recovery is checkpointing database 'test2' (58) > > Why do you think these are "errors"? The sql server log file contains > messages, some of which may be errors but many of which are not. The > messages you see are standard messages that indicate a successful restore > (btw - I don't think you posted all the relevant messages since there should > be a "Database restored: Database: <dbname>, creation ..." message. > > > "Kristen" <Kris***@discussions.microsoft.com> wrote in message There isn't anything wrong and you can't directly control these messages. news:D9C48AE9-91FC-4752-94CB-0428A569F826@microsoft.com... > No I didn't post all the messages. The database did successfully restore. > I > want to understand what I am doing wrong when restoring these databases so > the messages are not written to the log. Most of the time I am taking a > backup of 1 database and restoring it to another existing DB. Using the > GUI > for the restore. > Any ideas? These messages are not errors. Again, not everything written to the log is an error. And obviously I mean in a different DB name and not over the existing one ;)
Show quoteHide quote "Kristen" <Kris***@discussions.microsoft.com> wrote in message news:5365DC0E-0F94-4109-A028-E775E00E8A10@microsoft.com... >I tried doing it in TSQL........didn't work > > RESTORE DATABASE test2 > FROM DISK = 'E:\MSSQL\Backup\LVTS_Min_03122007.bak' > WITH RECOVERY, > MOVE 'LVTS_Min_Data' TO 'E:\MSSQL\Backup\test2_data.mdf', > MOVE 'LVTS_Min_Log' TO 'E:\MSSQL\Backup\test2_log.ldf' > > Bypassing recovery for database 'test2' because it is marked IN LOAD. > Starting up database 'test2'. > Recovery is checkpointing database 'test2' (58) > > > "Immy" wrote: > >> Try using the 'WITH RECOVERY' OPTION and issue the restore command via >> TSQL >> and not the Gui. >> >> "Kristen" <Kris***@discussions.microsoft.com> wrote in message >> news:9FE4EEAE-6332-4F67-BA23-6D1AA00878D3@microsoft.com... >> > Is it possible if I do not specify "Force over existing Database" that >> > it >> > can >> > cause this error? >> > >> > "Kristen" wrote: >> > >> >> I do restores on a daily basis. The restores are taken from DISK >> >> backups. I >> >> am not using backup devices. >> >> I am noticing all these errors in the log file: >> >> Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. >> >> When I do the restore, I am using the gui (rt click on database, >> >> select >> >> restore). >> >> Sometimes I need to restore over an existing DB, other times I restore >> >> to >> >> a >> >> new database. >> >> Any ideas? I want to make sure I am doing the restores correctly and >> >> remove >> >> these errors >> >> >> If I do RESTORE DATABASE test WITH RECOVERY
it doesn't actually do a restore from a backup....it just sets the RECOVERY option correct? Show quoteHide quote "Immy" wrote: > Try using the 'WITH RECOVERY' OPTION and issue the restore command via TSQL > and not the Gui. > > "Kristen" <Kris***@discussions.microsoft.com> wrote in message > news:9FE4EEAE-6332-4F67-BA23-6D1AA00878D3@microsoft.com... > > Is it possible if I do not specify "Force over existing Database" that it > > can > > cause this error? > > > > "Kristen" wrote: > > > >> I do restores on a daily basis. The restores are taken from DISK > >> backups. I > >> am not using backup devices. > >> I am noticing all these errors in the log file: > >> Bypassing recovery for database 'xxxxx' because it is marked IN LOAD. > >> When I do the restore, I am using the gui (rt click on database, select > >> restore). > >> Sometimes I need to restore over an existing DB, other times I restore to > >> a > >> new database. > >> Any ideas? I want to make sure I am doing the restores correctly and > >> remove > >> these errors > > >  
Other interesting topics
Troubleshooting High CPU
Trace flags for deadlock detection on startup. Deadlocks in the error log DATE RANGE ISSUE Is my SQL Server 2000 cluster 2+1 LAM enabled? Sql Server 2000 Agent Scheduled Job Write simple batch job to start SQL Server Service SQL Express on a small network IDENTITY limit Mail Profile |
|||||||||||||||||||||||
