Like NileshKumarSaha, you can go for either way to create a case from status of entries in table.
Those were true solutions but to understand how to decide on which 1 to choose...Lemme give you a pointer.
When you need an action to be done in the context of a case, go for standard agent as its transaction friendly.
When you need some action to be done on a schedule basis, choose advanced agents.
So in your scenario, it looks like a typical bulk processing. I am assuming the staging table you are using gets updated based on some bulk processing of file, or manual entries. And you are supposed to create cases based on the flag in the table.
So the concept works running the agent to run once a day or hourly basis based on the requirement.
So i would suggest using advanced agent for your scenario. Again you can queue it to standard agent from within the advanced agent activity for load balancing, like NileshKumarSaha suggested that point.
Thank you so much Guys for taking time out and answering my question.
Even I had this idea to use Advance agent because its just a row in the table. and I don't need AQM in this scenario, as if something failed, and the row status is not changed to "Processed", it will be picked up by another agent again.