Showing posts with label properties. Show all posts
Showing posts with label properties. Show all posts

Friday, March 30, 2012

Jobs

Hi,
Using Enterprise Manager, when i create a job, The job properties dialog box
has Schedules tab. In Schedules tab I have option to create New Altert.
I am trying to undrestand why would i need to create an alert in Job
Schadules.
Any help would be apprecited,
AliHi,
By setting an alert on a job, you can send a Email / Pager message to get
the status of your job.
Thanks
Hari
MCDBA
"A.M" <IHateSpam@.sapm123.com> wrote in message
news:eZuJTct3DHA.4060@.TK2MSFTNGP11.phx.gbl...
quote:

> Hi,
> Using Enterprise Manager, when i create a job, The job properties dialog

box
quote:

> has Schedules tab. In Schedules tab I have option to create New Altert.
> I am trying to undrestand why would i need to create an alert in Job
> Schadules.
> Any help would be apprecited,
> Ali
>
|||Hi Ali,
Thank you for using MSDN Newsgroup!
I would like to follow up on this issue and see if you still have questions
about this issue. Should you have any questions, please feel free to post
here. Looking forward to your reply!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Wednesday, March 21, 2012

Job NextRunDate using DMO always 0

Hi All,
I'm having a problem where whenever I add a new job (in code) with a
schedule to our server, the NextRunDate and NextRunTime properties are
always 0.
I have tried executing the sp_help_jobschedule stored procedure, but the
values returned are still 0.
I noticed that when i did a refresh on the job object itself when i was
using SQL Server 2000 SP4, the nextRunDate and time were calculated
correctly, however, we are not moving to SP4 and are staying on SP3a, so
that doesn't really help me.
Hope you can help.
Thanks,
BenHi
Just wondering if sp_help_job gives you the correct schedule?
John
"Ben Brearley" wrote:

> Hi All,
> I'm having a problem where whenever I add a new job (in code) with a
> schedule to our server, the NextRunDate and NextRunTime properties are
> always 0.
> I have tried executing the sp_help_jobschedule stored procedure, but the
> values returned are still 0.
> I noticed that when i did a refresh on the job object itself when i was
> using SQL Server 2000 SP4, the nextRunDate and time were calculated
> correctly, however, we are not moving to SP4 and are staying on SP3a, so
> that doesn't really help me.
> Hope you can help.
> Thanks,
> Ben
>
>|||Hi John,
Yes sp_help_job does give me the correct schedule.
I found out that the problem was fixed in SP4, and it involves Jobs not
starting unless they are owned by an admin user.
I tested this with a domain admin account, and the Next run dates and times
appear perfectly.
So until we go to the latest service pack, i guess this problem will be
unresolved, unless we calculate these Dates and times ourselves.
Ben
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:83BE8BBE-FC78-41B0-8B4C-CBF419ADF44C@.microsoft.com...
> Hi
> Just wondering if sp_help_job gives you the correct schedule?
> John
> "Ben Brearley" wrote:
>|||Hi Beni
If sp_help_job shows the correct shedule use profiler to see what it calls
before it runs sp_help_jobschedule or run sp_help_job and discard the result
before running sp_help_jobschedule.
John
"Ben Brearley" wrote:

> Hi John,
> Yes sp_help_job does give me the correct schedule.
> I found out that the problem was fixed in SP4, and it involves Jobs not
> starting unless they are owned by an admin user.
> I tested this with a domain admin account, and the Next run dates and time
s
> appear perfectly.
> So until we go to the latest service pack, i guess this problem will be
> unresolved, unless we calculate these Dates and times ourselves.
> Ben
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:83BE8BBE-FC78-41B0-8B4C-CBF419ADF44C@.microsoft.com...
>
>

Monday, March 19, 2012

Job Failure External Log

Someone in this newsgroup has suggested turning on External Log to see the
job failure information as follow:
Job's properties, choose the step, click 'Edit' then choose 'Advanced' tab.
There would be 'Output file' field. Check if it is set and if it is, then
look at the file.
For a scheduled job failure, I find that there is no external log is
enabled. I would like to know where is the best place to put the external
log ? I don't want to mix it with other logs.
ThanksI would put it with the other logs, but name it differently or put it in a
sub-directory underneath the logs directory. There it will easier to find.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtHNrfpZFHA.464@.TK2MSFTNGP15.phx.gbl...
> Someone in this newsgroup has suggested turning on External Log to see the
> job failure information as follow:
> Job's properties, choose the step, click 'Edit' then choose 'Advanced'
tab.
> There would be 'Output file' field. Check if it is set and if it is, then
> look at the file.
> For a scheduled job failure, I find that there is no external log is
> enabled. I would like to know where is the best place to put the external
> log ? I don't want to mix it with other logs.
> Thanks
>

Job Failure External Log

Someone in this newsgroup has suggested turning on External Log to see the
job failure information as follow:
Job's properties, choose the step, click 'Edit' then choose 'Advanced' tab.
There would be 'Output file' field. Check if it is set and if it is, then
look at the file.
For a scheduled job failure, I find that there is no external log is
enabled. I would like to know where is the best place to put the external
log ? I don't want to mix it with other logs.
ThanksI would put it with the other logs, but name it differently or put it in a
sub-directory underneath the logs directory. There it will easier to find.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtHNrfpZFHA.464@.TK2MSFTNGP15.phx.gbl...
> Someone in this newsgroup has suggested turning on External Log to see the
> job failure information as follow:
> Job's properties, choose the step, click 'Edit' then choose 'Advanced'
tab.
> There would be 'Output file' field. Check if it is set and if it is, then
> look at the file.
> For a scheduled job failure, I find that there is no external log is
> enabled. I would like to know where is the best place to put the external
> log ? I don't want to mix it with other logs.
> Thanks
>

Job Failure External Log

Someone in this newsgroup has suggested turning on External Log to see the
job failure information as follow:
Job's properties, choose the step, click 'Edit' then choose 'Advanced' tab.
There would be 'Output file' field. Check if it is set and if it is, then
look at the file.
For a scheduled job failure, I find that there is no external log is
enabled. I would like to know where is the best place to put the external
log ? I don't want to mix it with other logs.
Thanks
I would put it with the other logs, but name it differently or put it in a
sub-directory underneath the logs directory. There it will easier to find.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtHNrfpZFHA.464@.TK2MSFTNGP15.phx.gbl...
> Someone in this newsgroup has suggested turning on External Log to see the
> job failure information as follow:
> Job's properties, choose the step, click 'Edit' then choose 'Advanced'
tab.
> There would be 'Output file' field. Check if it is set and if it is, then
> look at the file.
> For a scheduled job failure, I find that there is no external log is
> enabled. I would like to know where is the best place to put the external
> log ? I don't want to mix it with other logs.
> Thanks
>