database log truncated
-
We have a database that has full backup daily 2:30am, and transaction log backup daily at 12 noon. The database is in FULL recovery mode. Recently it has started truncating the database log a couple times a day. It seems to have enough space, the .LDF file isn't too big. Any ideas for why this is happening or suggestions for what else I should look at. Thanks a lot!
-
Does this message appear in the SQL Server log ?
Database log truncated: Database:
If so, someone is executing a "backup log with truncate_only"
Who has sa or database owner rights ?
SQL = Scarcely Qualifies as a Language
-
Does this message appear in the SQL Server log ?
Database log truncated: Database:
If so, someone is executing a "backup log with truncate_only"
Who has sa or database owner rights ?
SQL = Scarcely Qualifies as a Language
-
Does this message appear in the SQL Server log ?
Database log truncated: Database:
If so, someone is executing a "backup log with truncate_only"
Who has sa or database owner rights ?
SQL = Scarcely Qualifies as a Language
-
Does this message appear in the SQL Server log ?
Database log truncated: Database:
If so, someone is executing a "backup log with truncate_only"
Who has sa or database owner rights ?
SQL = Scarcely Qualifies as a Language
-
Hi, Can you see in the SQL Server logs if a Checkpoint is being issued. Also is the transaction log being truncated at regular intervals ? In SQL Server 7 there was a setting Truncate Log on Checkpoint. That setting is not there in SQL Server 2000. However and perhaps other people on this forum might correct me, but I think in FULL RECOVERY mode, SQL SERVER intermittently issues a checkpoint. Hope I am not causing confusion here.
-
Are you sure the truncation is a bad thing? Have you tried restoring your full backup, followed by each of your transaction log backups and see if things are all there?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply