I believe I finally figured it out. I was able to queue up 7 reports successfully without any errors or 'default' reports being pushed out. It all lies in the delay mechanism. The one posted here did not work at all for fileshare subscriptions. I referred to http://blogs.msdn.com/psssql/archive/2009/02/02/why-aren-t-my-subscriptions-working.aspx, http://blogs.msdn.com/deanka/archive/2009/01/13/diagnosing-and-troubleshooting-subscriptions.aspx, and finally http://spilich.blogspot.com/2007/11/using-data-driven-subscriptions-in.html. Basically you have two issues to contend with, one being that the job actually needs time to execute (usually about 1-3 seconds), and then you need time for the Event and Notifications tables to be processed. There are only two threads available, so slamming subscriptions one after another will not work and you end up with errors, uncustomized reports, and missing reports.

The delay mechanism I used is:

DECLARE @events int, @notifications int

--run the job

EXEC msdb..sp_start_job @job_name = @scheduleID

--give time for job to process and EVENT table to populate

WAITFOR DELAY ''00:00:02''

--make sure we limit how many subscriptions we run simultaneously

SELECT @events = COUNT(*) FROM ReportServer..Event WHERE (EventData = @SubscriptionID)

SELECT @notifications = COUNT(*) FROM ReportServer..Notifications WHERE (SubscriptionID = @SubscriptionID) --AND (ProcessHeartBeat IS NOT NULL)

WHILE (@events >= 1 OR @notifications >= 2)

BEGIN

--give some time for RS to pick up on pending subs in NOTIFICATIONS table

--i used 5 seconds since I know, on average, most reports I run take at least

--5 seconds (even though some may take a few minutes), so no need to check every second.

WAITFOR DELAY ''00:00:05''

SELECT @events = COUNT(*) FROM ReportServer..Event WHERE (EventData = @SubscriptionID)

SELECT @notifications = COUNT(*) FROM ReportServer..Notifications WHERE (SubscriptionID = @SubscriptionID) --AND (ProcessHeartBeat IS NOT NULL)

END

I am going to test this on a subscription with reports that consistently take 2-10 MINUTES a piece to run and see how it goes. But it definitely seems to work on smaller reports for the time being. I welcome your comments.