Achieving Parallelism and avoiding Concurrency - Need Design Advice

Question

Requirement:
Extract Data from the database using SSIS.
Design Details:
There are two tables
ReportExtract and ReportExtractQueue. ReportExtract is a reference table and contains all the details related to the extracts.
ReportExtractQueue is a Queue Table designed for SSIS Package to process the extracts as per priority.
2. The SSIS Package, at any point of time picks up only one ReportExtractID to process from ReportExtractQueue where the ProcessingStatus = ‘Q’ and the Priority is High (in ascending order). This is achieved
by calling a stored procedure which has logic as below.
DECLARE @ReportExtractID int;
SELECT @ReportExtractID = (SELECT TOP 1 ReportExtractID
FROM ReportExtractQueue
WHERE ProcessingStatus = 'Q' -- InQueue
ORDER BY Priority);
IF @ReportExtractID IS NOT NULL
BEGIN
UPDATE ReportExtractQueue
SET ProcessingStatus = 'P' --InProgress
WHERE ReportExtractID = @ReportExtractID
SELECT @ReportExtractID AS ReportExtractID
END;
3. Once the package picks up the ReportExtractID from the Queue, the ProcessingStatus is changed to ‘P’ (InProgress) and then processes the extract. After the Processing is complete the ProcessingStatus is
updated again to either ‘S’ (Success) / ‘F’ (Failed).
4. Scheduling for Parallel Execution: 
Four copies of the same SSIS Package are copied to four different folders.
Four Jobs are created, each referring to a copy of the SSIS Package.
The Jobs are scheduled to run every 15 minutes to poll the Queue table through SSIS package.
The Start Time for all the Jobs is same.
Problem: Since all the Jobs start at the same time and run every 15 minutes. How do I ensure each job picks up a unique ReportExtractID from the Queue table. So far, from what i tested in the test
environments I have not faced this issue. But I want to avoid Concurrency Issues on the Queue table.
If I use the rowlock, readpast hints on the Queue table, will it resolve the Concurrency Issues (if any).      
If yes, then should I use these hints even while updating the Processing Status? Should I follow any other design approach?.
Please advise
-- Praveen

Answer 1

The jobs will clash.
And the design is not scalabale.
SSIS is not the best solution here in general.
You better have the stored procedure pick records up and then run the processing package - many times, even in parallel - given this package
can tolerate multiple copies running. SQL Agent runs them in async mode, the package in Agent can start with sp_start_job
Arthur My Blog