InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 15:46:10 GMT20http://www.sqlservercentral.com/Forums/Topic1405871-1292-1.aspxHi,If you're trying to avoid log growth you could pre-size the transaction log to avoid auto-growth operations.AndrewTue, 29 Jan 2013 06:40:57 GMTAndrew Pruskihttp://www.sqlservercentral.com/Forums/Topic1405871-1292-1.aspxAt startup there a quite a few inserts that run. I wasn't sure if that would get the log to it's tipping point and then subsequently grow. Was really trying to avoid log growth.ThanksFri, 11 Jan 2013 04:21:20 GMTSQLSACThttp://www.sqlservercentral.com/Forums/Topic1405871-1292-1.aspx[quote][b]SQLSACT (1/11/2013)[/b][hr][quote][b]GilaMonster (1/11/2013)[/b][hr]Yes, you could have. The DB was online and available.[/quote]Thanks, would you recommend it though? [/quote]Yes, why not?[quote]Am I right in that the 3rd phase (Undo) is where the uncommitted transactions are being rolled back?[/quote]Yes[quote]I am assuming that if I had started the application, the Log would have grown?[/quote]Maybe. Maybe not. Does the log usually grow when you start the app?Fri, 11 Jan 2013 04:18:13 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1405871-1292-1.aspx[quote][b]GilaMonster (1/11/2013)[/b][hr]Yes, you could have. The DB was online and available.[/quote]Thanks, would you recommend it though? Am I right in that the 3rd phase (Undo) is where the uncommitted transactions are being rolled back?At the start of Phase 3, I noted that the log was 99% full, at about 70% of the 3rd phase, the usage went down to about 20% and after recovery, it was 1%.I am assuming that if I had started the application, the Log would have grown?ThanksFri, 11 Jan 2013 04:12:08 GMTSQLSACThttp://www.sqlservercentral.com/Forums/Topic1405871-1292-1.aspxYes, you could have. The DB was online and available.Fri, 11 Jan 2013 04:05:30 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1405871-1292-1.aspxHi AllI had a situation where my SQL Server was stopped in the middle of a long running transaction, I knew that when SQL Server came up, there would be a substantial wait before the database became available again.When SQL Server came up, the database was in a recovery state. I checked the logs and it showed "recovery of database.... Phase 2 of 3"What confused me is that after phase 2 of 3, the database went into and Online State but the logs showed "recovery of database.... Phase 3 of 3"I allowed phase 3 to complete before starting the application that uses the databaseMy question is, could I have started using the database during the 3rd phase already, was it unnecessary to have waited for phase 3 to complete?ThanksFri, 11 Jan 2013 03:59:14 GMTSQLSACT