# Architecture for Queuing Jobs from Database

**URL:** https://discuss.hangfire.io/t/architecture-for-queuing-jobs-from-database/2069
**Category:** question
**Created:** [May 31, 2016, 8:34pm UTC](https://discuss.hangfire.io/t/architecture-for-queuing-jobs-from-database/2069 "2016-05-31T20:34:00Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Jonah\_Simpson](https://dub1.discourse-cdn.com/flex017/user_avatar/discuss.hangfire.io/jonah_simpson/32/504_2.png) [@Jonah\_Simpson](https://discuss.hangfire.io/u/Jonah_Simpson)
#### Post date: [May 31, 2016, 8:34pm UTC](https://discuss.hangfire.io/t/architecture-for-queuing-jobs-from-database/2069/1 "2016-05-31T20:34:00Z")

</div>

Hey Folks,

Currently using Hangfire with MSMQ & SQl Server. Everything is working great in our current environment.

We have a requirement to be able to Enqueue one or more Jobs when we receive data into our database and I was wondering if there is any recommendations on patterns to make this happen?

I’m currently imagining a sql table with a Hangfire recurring job or IBackgroundProcess polling that table looking for work but this feels pretty brute force and I wanted to make sure that weren’t any more elegant/real-time solutions available. I don’t really have access to the code that does the insert into the database in the first place and I also don’t really want to get into any SQL Managed code execution.

Thanks in advance for any feedback/ideas.

Cheers,  
Jonah