| bio | website | |
|---|---|---|
| location | New York, NY | |
| age | 24 | |
| visits | member for | 1 year, 9 months |
| seen | yesterday | |
| stats | profile views | 2 |
|
Jan 18 |
comment |
Restore to a point between two full SQL Server backups Okay, this makes sense. Unfortunately I don't think it will work. After talking with my sysadmins, it seems that effectively transaction log backups were taken, but not stored. When doing a transaction log backup today, the resulting file is very small. This doesn't really make sense to me, because the LDF file is still somewhat large. But it seems to be the case that transaction logs are being cleared. |
|
Jan 18 |
comment |
Restore to a point between two full SQL Server backups This is how I understood the problem. The issue is that in step 3, my transaction log backup is really small, only about 400K. This can't possibly contain all the transaction data from a 10+ GB ldf file. |
|
Jan 17 |
awarded | Scholar |
|
Jan 17 |
accepted | Restore to a point between two full SQL Server backups |
|
Jan 17 |
comment |
Restore to a point between two full SQL Server backups @AaronBertrand Okay, I understand now. Thanks for your help. To be clear, I know to take transaction log backups, but as a developer who knows more SQL than our sysadmins, I've been charged with restoring their mistake. Thanks for your help Aaron. |
|
Jan 17 |
comment |
Restore to a point between two full SQL Server backups @AaronBertrand Okay, thanks for your help. It makes sense, it's just confusing because it seems like the transaction data is there, just inaccessible. I don't see why I can't take a transaction backup from the restored database. Please forgive my stubbornness. This is a noncritical situation, but I just don't completely how this works. |
|
Jan 17 |
comment |
Restore to a point between two full SQL Server backups @DaveE Got it. But then why is my ldf file so large? It's nearly as large as the mdf file, in the 10s of GB. I figured it must be holding the transaction data between backups. |
|
Jan 17 |
comment |
Restore to a point between two full SQL Server backups This is kind of what I thought, but I don't really understand why. The second full backup should have all of the transaction data, no? |
|
Jan 17 |
comment |
Restore to a point between two full SQL Server backups @RThomas If a mod thinks this would be better there, please move it. I don't want to double post. Although I guess I could delete this and repost there. |
|
Jan 17 |
comment |
Restore to a point between two full SQL Server backups @AaronBertrand Server1 was in full recovery mode. So when I restore I get ldf files. We do not have transaction log backups, otherwise I would be able to use those. |
|
Jan 17 |
asked | Restore to a point between two full SQL Server backups |
|
May 14 |
awarded | Editor |
|
May 14 |
revised |
Is using multiple foreign keys separated by commas wrong, and if so, why? Fixed title. |
|
May 14 |
suggested | suggested edit on Is using multiple foreign keys separated by commas wrong, and if so, why? |