Backups 1: 3 Common Strategies
Backing up SQL Server is different than backing up your conventional file or app servers. Databases have a few really big files, and you don’t want to back up the file itself, and the file is constantly changing, 24/7. Rather than file-level backups, you have 3 common choices: server-level snapshot backups, native full SQL Server backups, and transaction log backups. In this session, I’ll explain the pros and cons of each one, and explain where each one makes the most sense.
- Backups 2: Restores
- Backups 3: Setting Up Maintenance Plans
- Backups 4: Setting Up Ola Hallengren’s Maintenance Scripts
- Backups: Reading from Databases During Restores
- Configuration: Anti-Virus
- Configuration: Instant File Initialization
- Configuration: Lock Pages in Memory (LPIM)
- Configuration: Prepare for Emergencies with the Remote DAC
- Configuration: Sending Emails with Database Mail
- Configuration: sp_configure Settings
- Configuration: TempDB Files and Sizes
- Corruption 1: How it Happens, and How to Detect It
- Corruption 2: DBCC CHECKDB for VLDBs
- Maintenance: Agent Jobs
- Maintenance: Patches: Which Ones to Apply, When, and How
- Maintenance: Shrinking Files