Maintenance: Agent Jobs
SQL Server started long ago, and that’s why it has its own backups, emails, event logging, OS abstraction layer, and security. It invented wheels before a lot of operating systems had ’em. However, just because SQL Server has its own task scheduler – that’s Agent – doesn’t mean you should use it. Let’s cover when you should use it, and how.
- Backups 1: 3 Common Strategies
- 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: Patches: Which Ones to Apply, When, and How
- Maintenance: Shrinking Files
2 Comments. Leave new
Agent jobs that call SSIS packages, should also be okay within the agent? Or realistically SSIS should be on its own server? Sorry, if this is a bit out of scope.
That’s kinda out of scope for this class.