January 18, 2005 at 1:10 pm
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/ALeonard/howtocreateanasynchronousscheduleforareportserverr.asp
Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics
September 17, 2007 at 2:26 pm
This is great article.
But when i tried to follow the step as said, the job never got created in my "Reporting Services SQL Server Jobs".
Can you please let me know what rights need to be given and to which process ??
Thank you in Advance.
August 4, 2008 at 10:03 am
I was using this approach, but instead of renaming the job I created a new one and borrowed the step from the original job. I did this because I wanted to control multiple report refreshes from a single job. I deleted the "guid" named job. However, I noticed that the next day the "guid" named job was back.
(1) It would have been nice if Microsoft would give us the ability to name the job during the "configuration" creation.
(2) If the report execution configuration is turned off, the event behind the original job and now copied into the new one goes away. Micosoft could have done a better job here.
August 8, 2008 at 7:07 am
I now tried basically the same approach as the article. After renaming the “guid” named job to some meaningful name, I also disabled it and had the newly renamed job called by another. The idea was to have a “main” job call all the report refresh jobs as a single unit.
The problem is, the next morning I came in and all the “guid” jobs that were renamed are now back and enabled. Apparently, reporting services recreated them based on the schedule that was setup.
Is there some place within the reporting service database where the job names are referenced that could be adjusted to call the ‘renamed” version?
August 8, 2008 at 2:17 pm
Ok, got it working I think. The key is not to remove the schedule within the job but to simply disable the job.
August 11, 2008 at 7:19 am
Nope: The "guid" named jobs reappeared. It is like there is a nightly reporting servcie job that goes though and checks to see if the job exists and rebuilds it. I will try to just disable the job and see if that does the trick. regradless, it looks like I stuck with the "guid" names. I do have a query that helps identify the job to report:
select jobs.[name] as JobName,c.[name] as ReportName
from ReportServer$SQL2005.dbo.[catalog] as c
inner join ReportServer$SQL2005.dbo.[ReportSchedule] as rs
on c.ItemID = rs.ReportID
inner join msdb.dbo.sysjobs_view as jobs
on jobs.[name] = convert(varchar(100),rs.scheduleid)
order by jobs.[name]
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply