You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/sql/database-engine/replication/sql-transaction-log-grows.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,20 +81,20 @@ SELECT log_reuse_wait_desc FROM sys.databases WHERE name = '<your_cdc_database>'
81
81
4. To make sure that the transaction log can be reused, confirm that there is no other reuse reason indicated on the database:
82
82
83
83
```sql
84
-
SELECT log_reuse_wait_desc, NAME FROM sys.databases WHERE NAME = 'your_cdc_database'
84
+
SELECT log_reuse_wait_desc, NAME FROM sys.databases WHERE NAME = '<your_cdc_database>'
85
85
```
86
86
87
87
This returns output that resembles the following:
88
88
89
89
```output
90
90
log_reuse_wait_desc name
91
-
NOTHING your_cdc_database
91
+
NOTHING <your_cdc_database>
92
92
```
93
93
94
94
5. Now you should be able to truncate the Transaction log by using log backups. You should also be able to shrink the transaction log file to reduce the disk space that's consumed. For example, run the following:
95
95
96
96
```sql
97
-
BACKUP LOG your_cdc_database TO DISK='c:\folder\logbackup.trn'
97
+
BACKUP LOG <your_cdc_database> TO DISK='c:\folder\logbackup.trn'
0 commit comments