|
Comments
|
Charlie Bruno on
5/26/2010
Another excellent and highly informative video.
Thanks.
|
|
|
great video
|
|
|
good
|
|
|
Nice video, I have always wondered about why it creates those god awful names.
|
|
Kasey Wheeler on
5/26/2010
Good vid
|
|
|
Great video, can you post the script you wrote to the the name and the path?
|
|
|
never mind, I opened my eyes and found it under references.
|
|
|
Good coverage. i always curious what would happen if you renamed the jobs, but with so many other tasks at hand I felt it didnt require the indepth investigation. Id be curious if you do sucessfully figure out how to rename the jobs though.
|
|
|
Like seeing where we can shoot ourselves in the foot.
|
|
|
Helpful information.
|
|
Ralph Schwehr on
5/26/2010
usefull information as most dba's are running into these 'funky' subscription job names. Looking forward to see if these names can be changed :)
|
|
|
Excellent info, thank-you.
|
|
|
Certainly something we've all wondered about. Looking forward to what your further research shows regarding dependencies.
|
|
Anil Inampudi on
5/26/2010
gud one
|
|
|
Too bad MS didn't make these jobs stored in a separate domain, something akin to a different database schema.
Thanks for helping make sense of these jobs. We're just rolling out SSRS, and I can imagine users creating a ton of subscriptions in the future!
|
|
Peter Schott on
5/26/2010
Same as the others - GUIDs for job names are extrememly painful and make trying to set up Data-Driven subscriptions a painful experience.
|
|
|
Wonderful - loved showing the result of renaming the job.
|
|
|
Keep up the great work!
|
|
|
Very cool demo.
I've a demo with subscriptions and the way it works behind the scenes (DataBase), but in this perspective, this was very helpful.
|
|
|
Very cool demo.
I've a demo with subscriptions and the way it works behind the scenes (DataBase), but in this perspective, this was very helpful.
|
|
|
I am looking forward to the next installment! I would love to see a way to modify the job names without messing up anything. What would be even better is to find a way to create the jobs with clean names when the subscription is created initially so you don't have to go back in and modify the job names later.
|
|
|
Fascinating. Thanks for researching this.
|
|
Steve Culshaw on
5/29/2010
Excellent content, fingers crossed can find a way to consistently rename the Job
|
|
abdul samath on
5/30/2010
very useful
|
|
|
No sound heard
|
|
|
Very helpful. I created many subs but unable to find the issue when changed the name.
|
|
|
Andy,
I know you in the community and the amount of work you put in to build these communities over the years. We haven't met before and I have tremendous respect for you.
But the advice to change the job names here may not be a good one. Think of Reporting Services database as a system database and one shouldn't modify any part of it except using the supported api. If something breaks, I am sure it will then you MSFT will not support your case and one has to start over or go back to an older backup and loose work. The above is confirmed by the MSFT Reporting Services dev team also.
Also during version upgrades, RS database schema will change and expect the schema and data types to be changed in the next few iterations. I am saying this because RS database uses NTEXT extensively but the data type might be going away soon hopefully!
This is my opinion but you might disagree on this but throwing a word of caution here.
Later,
Sankar Reddy
|
|
|
great video!
|
|
|
Good!!
|
|
|
Good overview of some of the report scheduling processes
|