Understanding Logging & Recovery What Programmers Always Avoid Until it’s too Late! Kimberly L. Tripp Principal Mentor, Solid Quality Learning at President, SYSolutions, Inc. at me: and

Speaker – Kimberly L. Tripp Independent Consultant/Trainer/Speaker/Writer President, SYSolutions, Inc. Principal Mentor, Solid Quality Learning * In-depth, high quality training around the world! SQL Server MVP ( Microsoft Regional Director ( Writer/Editor for TSQL Solutions/SQL Magazine and Coauthor for MSPress title: SQL Server 2000 High Availability Presenter/Technical Manager for SQL Server 2000 High Availability Overview DVD (MS Part# ) Very approachable. Please ask me questions!

Possible Combinations Full  BULK_LOGGED doesn’t break automated backup procedures or log shipping. However, a log backup immediately before (when changing to Bulk Logged) and a log backup immediately after (when changing back to full) are recommended. Transitions to/from SIMPLE are NEVER recommended as they break the continuity of the log chain. This eliminates your ability to go back to a prior full…meaning you’re only as good as your last full backup! n/a Backup Log just prior to change Simple n/a No Change Required, Transaction Log Backup Recommended BEFORE B ulk_Logged No Change Required, Transaction Log Backup Recommended AFTER n/a Full SimpleBulk_LoggedFull From  To  Full Database or Differential backup after change Backup Log just prior to change Full Database or Differential backup after change

Resources Check out for information about upcoming events, useful downloads and excellent scripts! There are quite a few resources and/or links to use. MSPress title: SQL Server 2000 High Availability Authors: Allan Hirt with Cathan Cook, Kimberly L. Tripp, Frank McBath ISBN: Check out the main page of for a sample chapter to download!

Resources See for additional sample codewww.SQLSkills.com Articles in SQL Server Magazine, Aug/Sept 2003: Recovering from Isolated Corruption The Best Place for Bulk_Logged, InstantDoc #39782 Articles in SQL Server Magazine, Sept 2002: Before Disaster Strikes, InstantDoc ID#25915 Log Backups Paused for Good Reason, InstantDoc #26032 Restoring After Isolated Disk Failure, InstantDoc #26067 Filegroup Usage for VLDBs, InstantDoc #26031 Articles in TSQLSolutions Journal, Oct 2001: TSQLTutor Quick Tip: Saving Production Data from Production dBAs, InstantDoc ID#22073

Resources See and for articles on Backup/Restorewww.sqlmag.comwww.tsqlsolutions.com From Books Online “Home Page” select White Papers to get to msdn For Tech Net articles use: efault.asp?frame=true See for all sorts of stuff! Support Resources listed: Webcasts: cst&FR=0&SD=MSDN&LN=EN- US&CT=SD&SE=NONA cst&FR=0&SD=MSDN&LN=EN- US&CT=SD&SE=NONA

BOL Favorites Make sure to get the latest version of the BOL. See Technical Resources, Product Documentation “Switching Recovery Models” “ALTER DATABASE” Functions: OBJECTPROPERTY, SERVERPROPERTY, DATABASEPROPERTYEX “Using Recovery Models” “Checkpoints and the Active Portion of the Log” “Virtual Log Files” “Shrinking the Transaction Log” “Optimizing Transaction Log Performance”