Viewing 6 posts - 1 through 6 (of 6 total)
This service pack requires a reboot. Does anyone know whether or not the installation of SP3 can be done let's say during a saturday evening and the actual follow up...
June 11, 2009 at 9:09 am
There is a Cumulative update package for SQL Server 2008 that took care of the issue.
See http://support.microsoft.com/kb/956717/en-us for more info.
September 30, 2008 at 6:49 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....
August 11, 2008 at 7:19 am
Ok, got it working I think. The key is not to remove the schedule within the job but to simply disable the job.
August 8, 2008 at 2:17 pm
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...
August 8, 2008 at 7:07 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...
August 4, 2008 at 10:03 am
Viewing 6 posts - 1 through 6 (of 6 total)