Log file size growing
-
Hi,
My database log file size is growing day by day, even the database is configured as Simple and daily I am taking full backup. but its growing infinetly. Please help, I want to truncate the log file to 1-10 MB, currently its 9+ GB, now i've created a new log file and stopped growing limit of original log file but new file is also growing.
Regards,
GB
-
How big is the database? The transaction log will have to grow large enough to accomodate the largest transaction. In many cases this winds up being reindexing.
Generally, you don't want to shrink the transaction log file just to have it grow over and over again. There is quite a bit of overhead in allocating space as part of the transaction that needs the space...
That said, there might be an uncommitted transaction that's preventing the virtual log files from being truncated. Run DBCC OPENTRAN to see the oldest running transaction.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
-
Hi,
My problem solved by doing this:
1) CHECKPOINT
2) sp_repltrans (i got some pending records)
3) EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
4) backup log CPProduction WITH TRUNCATE_ONLY
5) DBCC SHRINKFILE ('DB_Log', ...)
But I don't understand 1 thing, I'd this problem on my subscriber server not on my publisher / distributor. but on subscriber, these commands run and show me the results.
Many thanks
Regards, GB
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply