---
title: 'How to Use a Persistent Job Store with Quartz'
source: 'https://youtube.com/watch?v=NsoCwY3XZdg'
video_id: 'NsoCwY3XZdg'
date: 2026-08-08
---

# How to Use a Persistent Job Store with Quartz

> Source: [How to Use a Persistent Job Store with Quartz](https://youtube.com/watch?v=NsoCwY3XZdg)

## Summary

This video provides a concise tip for developers using Quartz for background job processing: use a persistent job store backed by a SQL database to define and store jobs durably, then trigger them by name from your code.

### Key Points

- **Use a persistent job store** [00:00] — When using Quartz for background jobs, ensure you use a persistent job store, which can be any SQL database, to define and store jobs in the database.
- **Store durably with unique ID** [00:12] — Call 'store durably' and provide a unique identifier for each background job, then trigger it in code based on the job name.

### Conclusion

The key takeaway is to leverage Quartz's persistent job store with a SQL database for reliable, durable background job management, enabling job definition and triggering by name.

## Transcript

If you're using Quartz for running background jobs, make sure to use a persistent job store. You can use any SQL database, and this allows you to define and store your background jobs in the database.
You have to call store durably and give a unique identifier to your background job, and then you can trigger it in your code based on the job name.