Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit bbb947a

Browse files
Update docs/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002.md
Co-authored-by: William Assaf MSFT <wiassaf@microsoft.com>
1 parent 4a5b3da commit bbb947a

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

docs/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,8 @@ ms.custom: "seo-lt-2019"
3636
- Replication or availability group synchronization that is unable to complete
3737

3838

39-
If no recent transaction log history is indicated for the database with a full transaction log, the solution to the problem is straightforward: resume regular transaction log backups of the database.
39+
If no recent transaction log history is indicated for the database with a full transaction log, the solution to the problem is straightforward: resume regular transaction log backups of the database. For more information and a script to review backup history, see the section [Backing up the log](#backing-up-the-log) in this article.
40+
4041

4142

4243
## Resolving a full transaction log

0 commit comments

Comments
 (0)