|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Yesterday @ 9:17 AM
Points: 1,786,
Visits: 1,022
|
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 5:40 PM
Points: 5,123,
Visits: 20,370
|
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Monday, October 31, 2011 1:10 PM
Points: 480,
Visits: 1,163
|
|
Great article, great reading.
Now.. how can I manually activate/deactivate VLF's within a transaction log?
Thanks, S
--
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 4:08 PM
Points: 38,099,
Visits: 30,392
|
|
Slick84 (2/21/2011) Now.. how can I manually activate/deactivate VLF's within a transaction log? You can't. What are you trying to do?
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 4:08 PM
Points: 38,099,
Visits: 30,392
|
|
Thanks everyone. Glad you're enjoying it.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Monday, October 31, 2011 1:10 PM
Points: 480,
Visits: 1,163
|
|
It was just a question. I've seen that error before, I'll typically check the open trans and if/when the log was backed up.
It's most annoying when you see that error on a 'simple recovery' mode database. Specially common in QA/DEV DB's running on virtual machines.
--
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 4:08 PM
Points: 38,099,
Visits: 30,392
|
|
Slick84 (2/21/2011) It was just a question. I've seen that error before, I'll typically check the open trans and if/when the log was backed up.
Which will only help you if the reason is log backup, active transaction or replication
It's most annoying when you see that error on a 'simple recovery' mode database. Specially common in QA/DEV DB's running on virtual machines.
Hence one of the reasons for writing the article and mentioning the possible fixes for the causes. Log backups (and hence recovery model) is just one of many reasons for a full log.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Yesterday @ 10:14 PM
Points: 413,
Visits: 704
|
|
Thanks for the very informative article.
Running the first query I see Simple Recovery model and 'ACTIVE_TRANSACTION' However, running DBCC OPENTRAN report "No active open transactions."
This doesn't seem to add up. My limited understanding is that the log still has an open transaction preventing reuse, but there aren't any transactions running.
Any pointers on what to do from here?
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, June 14, 2013 6:15 PM
Points: 8,
Visits: 220
|
|
| Hi Gail, Great article. However i have 1 question; Are you saying that when one issue the command backup log db_name with truncate_only it backs up the active portion and releases the space for re-use ? so the backup chain is not broken ?
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Yesterday @ 3:00 PM
Points: 1,560,
Visits: 1,408
|
|
david.howell (2/21/2011) Thanks for the very informative article.
Running the first query I see Simple Recovery model and 'ACTIVE_TRANSACTION' However, running DBCC OPENTRAN report "No active open transactions."
This doesn't seem to add up. My limited understanding is that the log still has an open transaction preventing reuse, but there aren't any transactions running.
Any pointers on what to do from here?
Sys.databases isn't going to be updated as soon as the transaction completes. Try running a checkpoint in the database.
My blog: SQL Soldier Twitter: @SQLSoldier Microsoft Certified Master: SQL Server 2008 Sr. Product Consultant and Chief SQL Server Evangelist @ Idera My book: Pro SQL Server 2008 Mirroring
|
|
|
|