vacuum_database

Optimize database storage and performance.

Performance Impact:

Reclaims unused space
Rebuilds indexes
Updates statistics
Optimizes query plans
May take several minutes

When to Use:

After bulk operations (creates/deletes)
During maintenance windows
When performance degrades
After large deletions
Before major operations

Best Practices:

Run during low activity
Monitor space usage
Schedule regularly
Backup before running
Check performance impact
Allow sufficient time
Monitor system resources

Resource Usage:

CPU: Moderate to high
Memory: Temporary increase
Disk I/O: Heavy
Storage: Temporary spike

Example: { "analyze": true, "reasoning": "Running optimization after bulk task deletion to reclaim space and update query statistics for better performance." }

Input Schema

Name	Required	Description	Default
`analyze`	No	Whether to analyze after vacuum for query optimization. Note: This operation: - Reclaims unused space - Updates statistics - May take time for large datasets - Improves query performance
`reasoning`	No	Explanation for vacuum operation. Best practices: - Document performance issues - Note recent bulk operations - Record space reclamation goals - Track optimization results

Input Schema (JSON Schema)

{
  "properties": {
    "analyze": {
      "default": true,
      "description": "Whether to analyze after vacuum for query optimization.\nNote: This operation:\n- Reclaims unused space\n- Updates statistics\n- May take time for large datasets\n- Improves query performance",
      "type": "boolean"
    },
    "reasoning": {
      "description": "Explanation for vacuum operation. Best practices:\n- Document performance issues\n- Note recent bulk operations\n- Record space reclamation goals\n- Track optimization results",
      "type": "string"
    }
  },
  "type": "object"
}

atlas-mcp-server

vacuum_database

Input Schema

Input Schema (JSON Schema)

Other Tools