DBCC LOGINFO

Question

Post reply

DBCC LOGINFO

tony28

SSCertifiable

Points: 7112
More actions
April 5, 2014 at 2:26 am

#290011

Hello,
I checked my log and output from this was about 1400rows..
I did backup full, then log and shring according to some manual
Then I again did size like before.
Now I have just 12rows.
What is means directly?
I read that is for example lot of autogrow or old backup or something..
Can someone explain me ?
thank you

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Perry Whittle SSC Guru Points: 234013 More actions · Answer 1

what size did you shrink the file too?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

tony28 SSCertifiable Points: 7112 More actions · Answer 2

Perry Whittle (4/5/2014)
what size did you shrink the file too?

Now I dont understand.

I read that more than 100rows can cause problem with INSERT, UPDATE, DELETE. I was suprised if I saw more than 1400rows.

The Log file was about 20GB, I could shrink just for 13GB..

If I executed DBBC LOGINFO, there were about 1400rows

After backup log directly with statements ( not with Tivoli manager program ) it was possible shrink less to 100MB and these files were removed.

After this I did same size for log, because during rebuild index I saw that log has about 20GB..

after this I executed DBBC LOGINFO again and there were 28rows

Igor Micev SSC-Dedicated Points: 33109 More actions · Answer 3

Hi

1400+ virtual log files is a high fragmentation into the log file(s).

These three articles should be enough to understand how to configure your log

http://www.sqlskills.com/blogs/kimberly/transaction-log-vlfs-too-many-or-too-few/

http://www.sqlskills.com/blogs/kimberly/8-steps-to-better-transaction-log-throughput/

http://www.sqlskills.com/blogs/paul/bug-log-file-growth-broken-for-multiples-of-4gb/

Regards,

Igor

Igor Micev,My blog: www.igormicev.com

tony28 SSCertifiable Points: 7112 More actions · Answer 4

Igor Micev (4/5/2014)
Hi
1400+ virtual log files is a high fragmentation into the log file(s).
These three articles should be enough to understand how to configure your log
http://www.sqlskills.com/blogs/kimberly/transaction-log-vlfs-too-many-or-too-few/
http://www.sqlskills.com/blogs/kimberly/8-steps-to-better-transaction-log-throughput/
http://www.sqlskills.com/blogs/paul/bug-log-file-growth-broken-for-multiples-of-4gb/
Regards,
Igor

Thank you