Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

DBCC LOGINFO Expand / Collapse
Author
Message
Posted Saturday, April 5, 2014 2:26 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 2:15 PM
Points: 175, Visits: 515
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
Post #1558703
Posted Saturday, April 5, 2014 4:51 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 10:46 AM
Points: 6,370, Visits: 13,706
what size did you shrink the file too?

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

"Ya can't make an omelette without breaking just a few eggs"
Post #1558711
Posted Saturday, April 5, 2014 5:30 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 2:15 PM
Points: 175, Visits: 515
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
Post #1558714
Posted Saturday, April 5, 2014 7:04 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 6:19 AM
Points: 2,963, Visits: 2,982
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,
SQL Server developer at Seavus
www.seavus.com
Post #1558731
Posted Saturday, April 5, 2014 8:54 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 2:15 PM
Points: 175, Visits: 515
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
Post #1558735
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse