June 24, 2009 at 3:26 am
Hi,
I was wondering as to whether DBCC REINDEX is log shippied and applied during the restore on the secondary. I assume it is, I'm assuming everything applied to the primary is logshipped.
Thanks in advance
Russell Morgan
June 24, 2009 at 5:34 am
Yes it does(I tested it way back) .This is because everyhing is logged in the log file first (as per copy on write principle) and the database is in full recovery mode.The same log is then applied to the stand by database / inrecovery database.
Regards
Abhay Chaudhary
Sr.DBA (MCITP/MCTS :SQL Server 2005/2008 ,OCP 9i)
June 24, 2009 at 6:29 am
DBCC REINDEX is deprecated in SQL Server 2005 and 2008. It will be removed from the next version, you should use ALTER INDEX instead. All logged operations will be log-shipped - in FULL or BULK LOGGED recovery mode.
Copy on write does not apply to logging - you were perhaps thinking of database snapshots. Write-Ahead Logging (WAL) is the principle used with logging.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
June 24, 2009 at 9:50 pm
You are correct Paul ..its indeed WAL (So silly of me).
In the haste we miss the reality 🙂
Regards
Abhay Chaudhary
Sr.DBA (MCITP/MCTS :SQL Server 2005/2008 ,OCP 9i)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply