January 27, 2006 at 3:53 pm
I have a small database that I am using for testing a log backup script that is supposed to backup the log if the percentage of the log used is greater than a given percentage.
I am running SQL2K SP4 Standard Edition on a Windows 2003 server.
I am running a simple script to load a table with 50,000 records to make the log fill up.
I have, many times, verified that my recovery model is set to FULL. I see this in EM and when run the DATABASEPROPERTYEX command with the Recovery option. They all say FULL.
While my script was running, I was repeatedly running, in QA, DBCC SQLPERF(LOGSPACE). I could watch my log filling up but every time I saw 69.### percent get hit, it would all of a sudden drop back down to almost nothing.
I would expect this with a SIMPLE recovery model but not FULL.
Anybody got any ideas why this might be happening?
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
January 27, 2006 at 5:40 pm
If the log is set to auto-grow, the percentage will drop at the point where the log expansion has occurred. That's a guess, not a certainty, since I'm not on a system I can test with today. Or a scheduled log dump happens and truncates the committed portion of the log, though I'd expect that to happen at timed intervals rather than some threshold percentage.
January 27, 2006 at 8:39 pm
The log is only 10 MB and it is set to auto-grow but when the percentage would drop it would drop from around 70% down to about 20% but the log never grows.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply