SQL Server 2008 log file size is large and growing rapidly

Question

In most cases, users end up in a database for reading news. For transactions, very few queries are performed. 95% of database calls will be read-only.

The size of the log files in my database is growing 1 GB per day. Even if I compress the database, the size of the log file does not decrease. What could be causing the log file to grow larger? How can I control this? According to my knowledge log file does not increase when we read data from tables.

Any suggestions on how to work with the log file? How can you keep a manageable or reasonable size? Does this effect on performance?

Answer 1

There are a few things to consider. What types of backups do you make and what types of backups do you need. If you have an answer to this question, you can switch the recovery mode to simple or leave it filled, but then you need to do incremental backups on a daily basis (or whatever you do with the size of the log).

To set up database logging to simple (but only if you are doing a full backup of your database!).

• Right click in your database
• Select Properties
• Select Options
• Set recovery mode to simple

, , . , ( ).

Grandeather & Father & Son, , , /STRONG > . . 1 , 15 . , .

, , , ( 1- ​​ ). , .

Answer 2

, ( ) . , , . , , , . , , . , , . , . 15 .

BOL, , , . . , . , , , , , . - .

Answer 3

? / , SQL Server .

Answer 4

The main reason for the large log file size is related to the bulk transaction in the database. To reduce the size of the log file, select the option to back up the transaction log after a certain period of time.