October 3, 2014 at 9:47 am
Haven't found anything on the net, so I assume this is not possible. Is there a SQL server setting to disable showing report server subscriptions in the SQL agent job list? I don't want to delete these subscriptions, but I could care less about seeing them in SQL Agent.
[font="Courier New"]____________________________________________________________________________________________
Remember as you walk down lifes road, don't forget to stop and pee on the bushes - Thordog[/font]
October 3, 2014 at 11:19 am
There isn't anyway that I'm aware of to limit the view in SSMS.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 10, 2014 at 6:44 am
I notice that each SQL Agent GUID ties out to an entry in the ReportServer database on the ReportSchedule table. Since I have dozens of scheduled jobs, all running at the same time (M-F at 7:00am), couldn't I consolidate all of those into one GUID and just alter the Agent Job to include all of the EXEC commands?
Example, one GUID entry in SQL Agent has this step...
exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b41104c0-deae-41f2-96e2-2b40e6b0c63b'
...and the only thing different between that one and the others that run at the same time is the @EventData parameter.
Can I just add all of them into one SQL Agent entry....
exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b41104c0-deae-41f2-96e2-2b40e6b0c63b'
exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='dc455b9e-8a00-4817-aa7e-baf0a032d08e'
etc,
ect,
ect...
Any opinions? NOTE: I set up all of the jobs so only I would be altering their schedule(s) in the future. I get that this could be a problem when other users set up jobs and I consolidated all of them. In that situation, if one changes their schedule complications could arise.
December 10, 2014 at 8:21 am
thisisfutile (12/10/2014)
I notice that each SQL Agent GUID ties out to an entry in the ReportServer database on the ReportSchedule table. Since I have dozens of scheduled jobs, all running at the same time (M-F at 7:00am), couldn't I consolidate all of those into one GUID and just alter the Agent Job to include all of the EXEC commands?Example, one GUID entry in SQL Agent has this step...
exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b41104c0-deae-41f2-96e2-2b40e6b0c63b'
...and the only thing different between that one and the others that run at the same time is the @EventData parameter.
Can I just add all of them into one SQL Agent entry....
exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b41104c0-deae-41f2-96e2-2b40e6b0c63b'
exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='dc455b9e-8a00-4817-aa7e-baf0a032d08e'
etc,
ect,
ect...
Any opinions? NOTE: I set up all of the jobs so only I would be altering their schedule(s) in the future. I get that this could be a problem when other users set up jobs and I consolidated all of them. In that situation, if one changes their schedule complications could arise.
In theory, yes, this should work. I personally wouldn't do that mainly because, depending on how you have your SSRS environment setup, others can create and alter subscriptions so this change would break that functionality. The other issue is that with each an individual job they run in parallel, at least the AddEvent SP is run in parallel, whereas putting them in one job serializes them.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 10, 2014 at 12:08 pm
Jack Corbett (12/10/2014)
... The other issue is that with each an individual job they run in parallel, at least the AddEvent SP is run in parallel, whereas putting them in one job serializes them.
Thanks for the feedback.
I think I see what you're saying. 40 individual schedules running 40 reports at exactly 7:00:00am is better than 1 schedule running 40 reports in series (7:00:01, 7:00:03, 7:00:05, etc)? For background, the 40 jobs are actually 4 very different reports, going out to 10 users at the same time. You're suggesting by serializing them with the same Agent schedule (a single GUID job listed in SQL Agent) they're going to run slower than if they all fired at exactly 7:00 where they'd possibly utilize SQL Server's parallel query capabilities? Am I understanding?
Truth be told, I'm in a very small office environment so I'm rarely worried about off-hours query execution speed but I'm truly trying to understand what you mean here.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply