April 2, 2009 at 9:22 am
We have a database on FULL recovery mode, for which we cut transaction-log backups every 10 minutes.
While shrinking a 50-gb DATA file yesterday, I noticed that large transaction-log backups (5-10 gb each) were being created.
Can the shrinking of database files cause the transaction log to bloat like this?
This issue is discussed somewhat in the link below, but I would like some more information and a confirmation:
http://www.sqlservercentral.com/Forums/Topic460341-24-1.aspx
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 2, 2009 at 7:39 pm
Yes, it is possible as DBCC SHRINKFILE is logging database file page movement information in log file.
MJ
April 3, 2009 at 3:30 am
good post, I was not aware of the fact.
Rajesh Kasturi
April 5, 2009 at 3:36 pm
MANU (4/2/2009)
Yes, it is possible as DBCC SHRINKFILE is logging database file page movement information in log file.MJ
Thank you for the input.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply