Questions about SQL Server database transaction logs

Questions about SQL Server database transaction logs cannot be found in the experiment environment of SQL SERVER: SQLSERVER2005SP4. Windows 7 was not in the mood to write articles. No one looked at it anyway. Regarding the problems mentioned in my article, some of the answers can be found from the end of the MSDN article, while some have no answers. According to this article on the CSDN blog

Questions about SQL Server database transaction logs cannot be found in the experiment environment of SQL SERVER: SQLSERVER2005 SP4. Windows 7 was not in the mood to write articles. No one looked at it anyway. Regarding the problems mentioned in my article, some of the answers can be found from the end of the MSDN article, while some have no answers. According to this article on the CSDN blog

Questions about SQL Server database transaction logs

Cannot touch SQLSERVER

Lab environment: SQLSERVER2005 SP4, Windows7

I was not in the mood to write an article, but no one was reading it. Some of the questions mentioned in my article can be found from the MSDN at the end of the article, and some have no answers yet.

According to this article on the CSDN blog, you can take a look at the Hong Kong virtual host and website space before continuing to look at it, because some content in the CSDN blog will be referenced below

SQL Server transaction log Introduction

The first question: why does the number of Transaction log records increase when I completely back up the database? Why does the number of Transaction log records increase when I back up the database again and decrease when I back up the database again?

After the backup, it becomes 100 rows of records

Sometimes 50 rows of records are not fixed, and sometimes 50 rows of records are changed when you back up again.

The number of virtual log files is reduced, from 45 to 35.

After backup

I backed up the data like this.

After I back up the transaction log and truncate the log, the remaining 10 lines are record. backing up the transaction log will not reduce the physical size of the transaction log, so you need to shrink the transaction log.

After each full backup, log space used increases.

1 dbcc sqlperf (LOGSPACE), virtual host