Skip to content

Commit d0e4eeb

Browse files
authored
minor change of versions location and a missing backslash
1 parent cff5ece commit d0e4eeb

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ ms.custom: "seo-lt-2019"
2121
---
2222
# Troubleshoot a Full Transaction Log (SQL Server Error 9002)
2323

24+
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
25+
26+
2427
**Option 1: Follow the steps directly in a notebook via Azure Data Studio**
2528

2629
> [!div class="nextstepaction"]
@@ -31,7 +34,7 @@ ms.custom: "seo-lt-2019"
3134

3235
**Option 2: Follow the step manually**
3336

34-
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
37+
3538
This topic discusses possible responses to a full transaction log and suggests how to avoid it in the future.
3639

3740
When the transaction log becomes full, [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] issues a **9002 error**. The log can fill when the database is online, or in recovery. If the log fills while the database is online, the database remains online but can only be read, not updated. If the log fills during recovery, the [!INCLUDE[ssDE](../../includes/ssde-md.md)] marks the database as RESOURCE PENDING. In either case, user action is required to make log space available.
@@ -131,7 +134,7 @@ BEGIN
131134
BEGIN
132135
select 'Is '+ @recovery_model_desc +' recovery model the intended choice for your database? Review recovery models and determine if you need to change it. https://docs.microsoft.com/sql/relational-databases/backup-restore/recovery-models-sql-server'
133136
select 'To truncate the log consider performing a transaction log backup on database ''' + @dbname+ ''' which is in ' + @recovery_model_desc +' recovery model. Be mindful of any existing log backup chains that could be broken' as Recommendation
134-
select 'BACKUP LOG [' + @dbname + '] TO DISK = ''some_volume:\some_folder' + @dbname + '_LOG.trn''' as BackupLogCommand
137+
select 'BACKUP LOG [' + @dbname + '] TO DISK = ''some_volume:\some_folder\' + @dbname + '_LOG.trn''' as BackupLogCommand
135138
END
136139
else if (@log_reuse_wait = 3)
137140
BEGIN

0 commit comments

Comments
 (0)