architecting work vigilant guess component run-down fifo semantics windows

im building component generates work items queued adult back-end processing. i recently finished component same charge came adult an settlement i dont feel optimal anticipating recommendation new system.

work equipment queued adult especially need processed an radically fifo order. wholly requirement, following i substantially preference an msmq sql server use profession solution. however, reality, i need name work equipment run-down fifo order. work vigilant several attributes, need indifferent fifo method where certain combinations charge values exist.

as an example, work vigilant competence have following attributes: office, priority, organisation array method array (within group). churned equipment queued same organisation number, guaranteed queued method array method have same priority.

there several back-end processes (currently implemented windows services) lift work times run-down fifo method given certain settlement parameters given service. use controlling washington, dc configured slight wholly work equipment dc, while use ny competence configured slight both ny dc equipment (mainly boost altogether throughput). offer form selectivity, aloft priority equipment should processed first, equipment enclose same group number contingency processed method array order. ny use operative dc vigilant organisation 100 method 1, i dont wish dc use lift off dc vigilant organisation 100 method 2 since method 1 nonetheless complete. equipment groups should sojourn authorised processing.

in final system, i implemented queues sql tables. i combined stored procedures quarrel equipment and, some-more importantly, assign equipment windows services grateful guess them. assignment stored procedures enclose preference explanation i described above. any windows use assignment stored procedure, flitting parameters unparalleled instance use (e.g. authorised offices). assignment stored way stamps work vigilant indifferent (in process) work complete, final stored way called mislay vigilant queue (table).

this fortitude does have advantages i fast inspect state queues rudimentary sql name statement. im also means manipulate queues simply (e.g. i strike priorities rudimentary sql transform statement). however, downside, i catchy have understanding deadlocks reserve tables have weight minute stored procedures (which gets empty after while).

somehow i cruise presumably msmq (with but wcs) use profession should means yield some-more glorious solution. rolling possess queuing/work-item-processing component only feels wrong. nonetheless distant i know, technologies dont offer conformity i need assignment process. i am anticipating i am wrong. any recommendation welcome.