August 2, 2005 at 7:20 am
We have implemented Log shipping for our live databases. Of late, we notice that some of the databases in the secondary server often slip into "Loading" mode and remain as such for a very long time, after which we have to restore the DB from the full backup in the Primary Server.
Any idea, why this happens?
- Databases are relatively small (around 25 mb) and space is not the issue.
- While the DB is in the "loading" status, log shipping appears to run well (Log Shipping Monitor says so).
- Schema changes were NOT done in these DBs.
Any help would be much appreciated.
August 3, 2005 at 5:52 am
Hi,
what kind of logshipping did you implment, "out of the box" or "custom made"?
If the copying process overlaps with the restore the restore may fail and the database remains "loading"...
Something keeps the restore from finishing properly. Is msdb on autogrow? Do you execute sp_delete_backuphistory regularly?
regards karl
Best regards
karl
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply