Geek asks and answers

Microsoft SQL Server What does it mean that the transaction log is full?

What does it mean that the transaction log is full? I have a file that will grow by 20% if necessary. I have 4 GB left on the disk. How can I solve this problem forever? Running these commands temporarily resolves the issue:

DBCC SHRINKFILE ('MyDatabase_log', 1)
BACKUP LOG MyDatabase WITH TRUNCATE_ONLY
DBCC SHRINKFILE ('MyDatabase_log', 1)
+3
source share
8 answers

- , SQL- "" , - , ( , ... , , ), "", "" , "CheckPoint" - , "" ... . , ( "" ), , , "ok", CheckPopint , "" - . CheckPoint ... , ...

, " ", , , . , , , , .

, , ...

, , , , "" ( ) , (Incremental Full), .... ... ... ...

+7

, . - , - , . , .

( , ), "", TLog .

: , "Bulk-Logged" .

+3

SQL Server. , "", /.

+2

, .

+2

, , .

+2

, . . , , .

+1

20% . , . - , , 100 , 20 - , , ... , - , 100 , , , .

0

. .

, , , .

SQL Server 2005 Simple (/ ), DEV TEST, , , . .

SQL Server 2000 script, , :

BACKUP LOG MyDatabase WITH TRUNCATE_ONLY

In production environments, we usually have an hourly backup of the transaction log and a daily full backup planned in the database maintenance plans. This leads to a reduction in the transaction log to a reasonable size (the size that contains transaction data for 1 hour, obviously).

0
source

More articles:


All Articles