March 22, 2012 at 9:34 am
Just so you know, you probably won't be able to restore any log files to that database if there is a source a database from which tlog backups may come from in the future.
Just curious if you talked to the customer about this database and if there was a source database from which additional t-log backups may be taken and need to be applied to this warm standby database.
March 22, 2012 at 9:37 am
Lynn Pettis (3/22/2012)
Just so you know, you probably won't be able to restore any log files to that database if there is a source a database from which tlog backups may come from in the future.Just curious if you talked to the customer about this database and if there was a source database from which additional t-log backups may be taken and need to be applied to this warm standby database.
Yes..Customer will have additional T logs coming in and he will restore it when ever necessary..he has his own FTP jobs and restoration jobs..
Can you tell me, why wouldn't we be able to restore any more log files? DB is still in standby mode which should take log files right?
what can be the solution for my problem then?
March 22, 2012 at 9:43 am
Simple, you took the database out of standby doing the RESTORE DATABASE WITH RECOVERY.
Backing up the database and restoring it in STANDBY mode won't let it take additional t-log backups from the source database.
March 22, 2012 at 9:46 am
Benki Chendu (3/22/2012)
Lynn Pettis (3/22/2012)
Just so you know, you probably won't be able to restore any log files to that database if there is a source a database from which tlog backups may come from in the future.Just curious if you talked to the customer about this database and if there was a source database from which additional t-log backups may be taken and need to be applied to this warm standby database.
Yes..Customer will have additional T logs coming in and he will restore it when ever necessary..he has his own FTP jobs and restoration jobs..
Can you tell me, why wouldn't we be able to restore any more log files? DB is still in standby mode which should take log files right?
what can be the solution for my problem then?
From my previous post:
RESTORE DATABASE [databasename] WITH RECOVERY
After this, the database will be active and no more t-logs can be applied. If this is not what you need, then add the users to the source database, do a t-log backup there and apply all necessary t-logs including the last one ensuring that you use WITH STANDBY if you still want the database ready to accept additiional t-log backups.
You are going to need a full backup from the source database (after adding the users you need) and restoring that in STANDBY. After that, t-log backups taking after that full backup can be applied.
March 22, 2012 at 9:51 am
ok got the point..
Now, if the customer doesn't need any more logs to be restored, will it work for him with the new username?
March 22, 2012 at 3:52 pm
If you left the database in standby mode then the users (even the new one) will not be able to access the database. If you have taken a backup of this database after adding the user and then restored from that backup leaving in Standby then you will NOT be able to add new transaction logs from the source database.
Like Lynn said, you need to restore a backup of the source system to be able to apply more transaction logs from the source database.
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply