SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


HOWTO: Create an Asynchronous Schedule For a Report Server Report


HOWTO: Create an Asynchronous Schedule For a Report Server Report

Author
Message
Andy Leonard
Andy Leonard
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2427 Visits: 1102
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/ALeonard/howtocreateanasynchronousscheduleforareportserverr.asp

Andy Leonard
Data Philosopher, Enterprise Data & Analytics
Nitesh R Dedhia
Nitesh R Dedhia
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 4
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.

dasundell
dasundell
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 157
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.
dasundell
dasundell
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 157
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?
dasundell
dasundell
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 157
Ok, got it working I think. The key is not to remove the schedule within the job but to simply disable the job.
dasundell
dasundell
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 157
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]
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search