We have a ton of jobs that we run from time to time and I am trying to
figure out a way to let me know who executes a job and when. Would anyone
have any ideas they would be willing to share?
Thanks,
Jeff
If I understand correctly, this would basically be an email sent to whoever
saying this job has started. How about an approach where everytime this job
is executed, a row gets written to a log table?
"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
news:392901c48f88$950e40c0$a501280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> Assuming that all jobs are configured with SQL Agent, you
> could implement automatic notifications using a MAPI
> client. You will have to configure a MAPI client and then
> configure the Agent to use that profile and then configure
> each job for notification.
> hth
> DeeJay
> am trying to
> when. Would anyone
|||Job execution does get sent the job history tables. You could query those.
Another method that may be more conducive to what you are after is to create
a DTS package that uses VBScript, that pushes information to an outside
logfile. Then add that DTS package as steps to your job and send it
whatever data you want to push out.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Jeff" <jeff.southworth@.verizon.net> wrote in message
news:u8s0iu4jEHA.3896@.TK2MSFTNGP15.phx.gbl...
> If I understand correctly, this would basically be an email sent to
whoever
> saying this job has started. How about an approach where everytime this
job
> is executed, a row gets written to a log table?
> "DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
> news:392901c48f88$950e40c0$a501280a@.phx.gbl...
>
|||You understood properly.
Here is the approach similar to yours:
You can do this ways (one is done by default):
1. Go into the SQLServerAgent Properties and towards the
bottom under 'Error log', check 'Include execution trace
messages'. This will write all trace messages in the
SQLServerAgent log. This is not recommended since the log
can get quite large and should be only done for
troubleshooting purposes.
2. This is done by default: All job execution history is
retained in the 'sysjobhistory' table in the msdb
database. You can get the job_id and query this table.
However, the options to log here must be specified
according to your needs. For example, how long the history
is kept by the job itself and if your SQLServerAgent is
configured to retain the job history and how long. The
agent job history retention is configured in the
SQLServerAgent properties under 'Job System' tab.
This should do the job.
I would go with option 2 and perhaps create a reporting
table to export data (query whatever you need) out the
sysjobhistory table and then run your reports.
hth
DeeJay
>--Original Message--
>If I understand correctly, this would basically be an
email sent to whoever
>saying this job has started. How about an approach where
everytime this job[vbcol=seagreen]
>is executed, a row gets written to a log table?
>"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
>news:392901c48f88$950e40c0$a501280a@.phx.gbl...
you[vbcol=seagreen]
then[vbcol=seagreen]
configure[vbcol=seagreen]
and I
>
>.
>
sql
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Wednesday, March 28, 2012
Question regarding the execution of jobs
We have a ton of jobs that we run from time to time and I am trying to
figure out a way to let me know who executes a job and when. Would anyone
have any ideas they would be willing to share?
Thanks,
JeffHi,
Assuming that all jobs are configured with SQL Agent, you
could implement automatic notifications using a MAPI
client. You will have to configure a MAPI client and then
configure the Agent to use that profile and then configure
each job for notification.
hth
DeeJay
>--Original Message--
>We have a ton of jobs that we run from time to time and I
am trying to
>figure out a way to let me know who executes a job and
when. Would anyone
>have any ideas they would be willing to share?
>Thanks,
>Jeff
>
>.
>|||If I understand correctly, this would basically be an email sent to whoever
saying this job has started. How about an approach where everytime this job
is executed, a row gets written to a log table?
"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
news:392901c48f88$950e40c0$a501280a@.phx.gbl...
> Hi,
> Assuming that all jobs are configured with SQL Agent, you
> could implement automatic notifications using a MAPI
> client. You will have to configure a MAPI client and then
> configure the Agent to use that profile and then configure
> each job for notification.
> hth
> DeeJay
> >--Original Message--
> >We have a ton of jobs that we run from time to time and I
> am trying to
> >figure out a way to let me know who executes a job and
> when. Would anyone
> >have any ideas they would be willing to share?
> >
> >Thanks,
> >Jeff
> >
> >
> >.
> >|||Job execution does get sent the job history tables. You could query those.
Another method that may be more conducive to what you are after is to create
a DTS package that uses VBScript, that pushes information to an outside
logfile. Then add that DTS package as steps to your job and send it
whatever data you want to push out.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Jeff" <jeff.southworth@.verizon.net> wrote in message
news:u8s0iu4jEHA.3896@.TK2MSFTNGP15.phx.gbl...
> If I understand correctly, this would basically be an email sent to
whoever
> saying this job has started. How about an approach where everytime this
job
> is executed, a row gets written to a log table?
> "DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
> news:392901c48f88$950e40c0$a501280a@.phx.gbl...
> > Hi,
> >
> > Assuming that all jobs are configured with SQL Agent, you
> > could implement automatic notifications using a MAPI
> > client. You will have to configure a MAPI client and then
> > configure the Agent to use that profile and then configure
> > each job for notification.
> >
> > hth
> >
> > DeeJay
> > >--Original Message--
> > >We have a ton of jobs that we run from time to time and I
> > am trying to
> > >figure out a way to let me know who executes a job and
> > when. Would anyone
> > >have any ideas they would be willing to share?
> > >
> > >Thanks,
> > >Jeff
> > >
> > >
> > >.
> > >
>|||You understood properly.
Here is the approach similar to yours:
You can do this ways (one is done by default):
1. Go into the SQLServerAgent Properties and towards the
bottom under 'Error log', check 'Include execution trace
messages'. This will write all trace messages in the
SQLServerAgent log. This is not recommended since the log
can get quite large and should be only done for
troubleshooting purposes.
2. This is done by default: All job execution history is
retained in the 'sysjobhistory' table in the msdb
database. You can get the job_id and query this table.
However, the options to log here must be specified
according to your needs. For example, how long the history
is kept by the job itself and if your SQLServerAgent is
configured to retain the job history and how long. The
agent job history retention is configured in the
SQLServerAgent properties under 'Job System' tab.
This should do the job.
I would go with option 2 and perhaps create a reporting
table to export data (query whatever you need) out the
sysjobhistory table and then run your reports.
hth
DeeJay
>--Original Message--
>If I understand correctly, this would basically be an
email sent to whoever
>saying this job has started. How about an approach where
everytime this job
>is executed, a row gets written to a log table?
>"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
>news:392901c48f88$950e40c0$a501280a@.phx.gbl...
>> Hi,
>> Assuming that all jobs are configured with SQL Agent,
you
>> could implement automatic notifications using a MAPI
>> client. You will have to configure a MAPI client and
then
>> configure the Agent to use that profile and then
configure
>> each job for notification.
>> hth
>> DeeJay
>> >--Original Message--
>> >We have a ton of jobs that we run from time to time
and I
>> am trying to
>> >figure out a way to let me know who executes a job and
>> when. Would anyone
>> >have any ideas they would be willing to share?
>> >
>> >Thanks,
>> >Jeff
>> >
>> >
>> >.
>> >
>
>.
>
figure out a way to let me know who executes a job and when. Would anyone
have any ideas they would be willing to share?
Thanks,
JeffHi,
Assuming that all jobs are configured with SQL Agent, you
could implement automatic notifications using a MAPI
client. You will have to configure a MAPI client and then
configure the Agent to use that profile and then configure
each job for notification.
hth
DeeJay
>--Original Message--
>We have a ton of jobs that we run from time to time and I
am trying to
>figure out a way to let me know who executes a job and
when. Would anyone
>have any ideas they would be willing to share?
>Thanks,
>Jeff
>
>.
>|||If I understand correctly, this would basically be an email sent to whoever
saying this job has started. How about an approach where everytime this job
is executed, a row gets written to a log table?
"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
news:392901c48f88$950e40c0$a501280a@.phx.gbl...
> Hi,
> Assuming that all jobs are configured with SQL Agent, you
> could implement automatic notifications using a MAPI
> client. You will have to configure a MAPI client and then
> configure the Agent to use that profile and then configure
> each job for notification.
> hth
> DeeJay
> >--Original Message--
> >We have a ton of jobs that we run from time to time and I
> am trying to
> >figure out a way to let me know who executes a job and
> when. Would anyone
> >have any ideas they would be willing to share?
> >
> >Thanks,
> >Jeff
> >
> >
> >.
> >|||Job execution does get sent the job history tables. You could query those.
Another method that may be more conducive to what you are after is to create
a DTS package that uses VBScript, that pushes information to an outside
logfile. Then add that DTS package as steps to your job and send it
whatever data you want to push out.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Jeff" <jeff.southworth@.verizon.net> wrote in message
news:u8s0iu4jEHA.3896@.TK2MSFTNGP15.phx.gbl...
> If I understand correctly, this would basically be an email sent to
whoever
> saying this job has started. How about an approach where everytime this
job
> is executed, a row gets written to a log table?
> "DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
> news:392901c48f88$950e40c0$a501280a@.phx.gbl...
> > Hi,
> >
> > Assuming that all jobs are configured with SQL Agent, you
> > could implement automatic notifications using a MAPI
> > client. You will have to configure a MAPI client and then
> > configure the Agent to use that profile and then configure
> > each job for notification.
> >
> > hth
> >
> > DeeJay
> > >--Original Message--
> > >We have a ton of jobs that we run from time to time and I
> > am trying to
> > >figure out a way to let me know who executes a job and
> > when. Would anyone
> > >have any ideas they would be willing to share?
> > >
> > >Thanks,
> > >Jeff
> > >
> > >
> > >.
> > >
>|||You understood properly.
Here is the approach similar to yours:
You can do this ways (one is done by default):
1. Go into the SQLServerAgent Properties and towards the
bottom under 'Error log', check 'Include execution trace
messages'. This will write all trace messages in the
SQLServerAgent log. This is not recommended since the log
can get quite large and should be only done for
troubleshooting purposes.
2. This is done by default: All job execution history is
retained in the 'sysjobhistory' table in the msdb
database. You can get the job_id and query this table.
However, the options to log here must be specified
according to your needs. For example, how long the history
is kept by the job itself and if your SQLServerAgent is
configured to retain the job history and how long. The
agent job history retention is configured in the
SQLServerAgent properties under 'Job System' tab.
This should do the job.
I would go with option 2 and perhaps create a reporting
table to export data (query whatever you need) out the
sysjobhistory table and then run your reports.
hth
DeeJay
>--Original Message--
>If I understand correctly, this would basically be an
email sent to whoever
>saying this job has started. How about an approach where
everytime this job
>is executed, a row gets written to a log table?
>"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
>news:392901c48f88$950e40c0$a501280a@.phx.gbl...
>> Hi,
>> Assuming that all jobs are configured with SQL Agent,
you
>> could implement automatic notifications using a MAPI
>> client. You will have to configure a MAPI client and
then
>> configure the Agent to use that profile and then
configure
>> each job for notification.
>> hth
>> DeeJay
>> >--Original Message--
>> >We have a ton of jobs that we run from time to time
and I
>> am trying to
>> >figure out a way to let me know who executes a job and
>> when. Would anyone
>> >have any ideas they would be willing to share?
>> >
>> >Thanks,
>> >Jeff
>> >
>> >
>> >.
>> >
>
>.
>
Question regarding the execution of jobs
Hi,
Assuming that all jobs are configured with SQL Agent, you
could implement automatic notifications using a MAPI
client. You will have to configure a MAPI client and then
configure the Agent to use that profile and then configure
each job for notification.
hth
DeeJay
>--Original Message--
>We have a ton of jobs that we run from time to time and I
am trying to
>figure out a way to let me know who executes a job and
when. Would anyone
>have any ideas they would be willing to share?
>Thanks,
>Jeff
>
>.
>If I understand correctly, this would basically be an email sent to whoever
saying this job has started. How about an approach where everytime this job
is executed, a row gets written to a log table?
"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
news:392901c48f88$950e40c0$a501280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> Assuming that all jobs are configured with SQL Agent, you
> could implement automatic notifications using a MAPI
> client. You will have to configure a MAPI client and then
> configure the Agent to use that profile and then configure
> each job for notification.
> hth
> DeeJay
> am trying to
> when. Would anyone|||Job execution does get sent the job history tables. You could query those.
Another method that may be more conducive to what you are after is to create
a DTS package that uses VBScript, that pushes information to an outside
logfile. Then add that DTS package as steps to your job and send it
whatever data you want to push out.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Jeff" <jeff.southworth@.verizon.net> wrote in message
news:u8s0iu4jEHA.3896@.TK2MSFTNGP15.phx.gbl...
> If I understand correctly, this would basically be an email sent to
whoever
> saying this job has started. How about an approach where everytime this
job
> is executed, a row gets written to a log table?
> "DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
> news:392901c48f88$950e40c0$a501280a@.phx.gbl...
>|||You understood properly.
Here is the approach similar to yours:
You can do this ways (one is done by default):
1. Go into the SQLServerAgent Properties and towards the
bottom under 'Error log', check 'Include execution trace
messages'. This will write all trace messages in the
SQLServerAgent log. This is not recommended since the log
can get quite large and should be only done for
troubleshooting purposes.
2. This is done by default: All job execution history is
retained in the 'sysjobhistory' table in the msdb
database. You can get the job_id and query this table.
However, the options to log here must be specified
according to your needs. For example, how long the history
is kept by the job itself and if your SQLServerAgent is
configured to retain the job history and how long. The
agent job history retention is configured in the
SQLServerAgent properties under 'Job System' tab.
This should do the job.
I would go with option 2 and perhaps create a reporting
table to export data (query whatever you need) out the
sysjobhistory table and then run your reports.
hth
DeeJay
>--Original Message--
>If I understand correctly, this would basically be an
email sent to whoever
>saying this job has started. How about an approach where
everytime this job
>is executed, a row gets written to a log table?
>"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
>news:392901c48f88$950e40c0$a501280a@.phx.gbl...
you[vbcol=seagreen]
then[vbcol=seagreen]
configure[vbcol=seagreen]
and I[vbcol=seagreen]
>
>.
>
Assuming that all jobs are configured with SQL Agent, you
could implement automatic notifications using a MAPI
client. You will have to configure a MAPI client and then
configure the Agent to use that profile and then configure
each job for notification.
hth
DeeJay
>--Original Message--
>We have a ton of jobs that we run from time to time and I
am trying to
>figure out a way to let me know who executes a job and
when. Would anyone
>have any ideas they would be willing to share?
>Thanks,
>Jeff
>
>.
>If I understand correctly, this would basically be an email sent to whoever
saying this job has started. How about an approach where everytime this job
is executed, a row gets written to a log table?
"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
news:392901c48f88$950e40c0$a501280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> Assuming that all jobs are configured with SQL Agent, you
> could implement automatic notifications using a MAPI
> client. You will have to configure a MAPI client and then
> configure the Agent to use that profile and then configure
> each job for notification.
> hth
> DeeJay
> am trying to
> when. Would anyone|||Job execution does get sent the job history tables. You could query those.
Another method that may be more conducive to what you are after is to create
a DTS package that uses VBScript, that pushes information to an outside
logfile. Then add that DTS package as steps to your job and send it
whatever data you want to push out.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Jeff" <jeff.southworth@.verizon.net> wrote in message
news:u8s0iu4jEHA.3896@.TK2MSFTNGP15.phx.gbl...
> If I understand correctly, this would basically be an email sent to
whoever
> saying this job has started. How about an approach where everytime this
job
> is executed, a row gets written to a log table?
> "DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
> news:392901c48f88$950e40c0$a501280a@.phx.gbl...
>|||You understood properly.
Here is the approach similar to yours:
You can do this ways (one is done by default):
1. Go into the SQLServerAgent Properties and towards the
bottom under 'Error log', check 'Include execution trace
messages'. This will write all trace messages in the
SQLServerAgent log. This is not recommended since the log
can get quite large and should be only done for
troubleshooting purposes.
2. This is done by default: All job execution history is
retained in the 'sysjobhistory' table in the msdb
database. You can get the job_id and query this table.
However, the options to log here must be specified
according to your needs. For example, how long the history
is kept by the job itself and if your SQLServerAgent is
configured to retain the job history and how long. The
agent job history retention is configured in the
SQLServerAgent properties under 'Job System' tab.
This should do the job.
I would go with option 2 and perhaps create a reporting
table to export data (query whatever you need) out the
sysjobhistory table and then run your reports.
hth
DeeJay
>--Original Message--
>If I understand correctly, this would basically be an
email sent to whoever
>saying this job has started. How about an approach where
everytime this job
>is executed, a row gets written to a log table?
>"DeeJay Puar" <deejaypuar@.yahoo.com> wrote in message
>news:392901c48f88$950e40c0$a501280a@.phx.gbl...
you[vbcol=seagreen]
then[vbcol=seagreen]
configure[vbcol=seagreen]
and I[vbcol=seagreen]
>
>.
>
Friday, March 9, 2012
Question on Job history
Please could someone enlight me.
In enterprise manager -> management-> jobs -> view history
I could normally see the historic runs of the jobs.
I have a server, for some reason, only hold one historic
record of each job. Each time a job is run the history is
then refreshed and delete with only the latest job remain.
Where can I set in Enterprise Manager so I could adjust
the amount of the history held for the jobs?
Thanks
AlexAlex Au wrote:
> Please could someone enlight me.
> In enterprise manager -> management-> jobs -> view history
> I could normally see the historic runs of the jobs.
> I have a server, for some reason, only hold one historic
> record of each job. Each time a job is run the history is
> then refreshed and delete with only the latest job remain.
See How to resize the job history log (Enterprise Manager)
http://msdn.microsoft.com/library/d...>
aem_8xpj.asp
Why not create Your Own SQL Server Job Management System?
http://www.sql-server-performance.com/rd_jobs.asp
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Sebastian
Thanks for this. I have checked and found that the Job
agent setting no different from other servers. I think the
real issue seem to be in the time the job history are
kept.. All the jobs that have only one history are only
run once a month, and I have jobs that run daily - they
have all the job history up to a month.
Alex
>--Original Message--
>Alex Au wrote:
>
history
is
remain.
>
>See How to resize the job history log (Enterprise Manager)
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>Why not create Your Own SQL Server Job Management System?
>http://www.sql-server-performance.com/rd_jobs.asp
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||The trouble is that if you have a job that runs very often e.g once every
minute, it can quickly eat up the 1000 rows that is the default job history
log size. This setting applies to the server so even if the job history rows
per job is 100, it will not honour this if the max history log size >1000.
Thus it might be worth lowering the rows per job and increasing the max log
size to find the balance that works for you.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2d9401c40075$21391820$a601280a@.phx.gbl...
> Sebastian
> Thanks for this. I have checked and found that the Job
> agent setting no different from other servers. I think the
> real issue seem to be in the time the job history are
> kept.. All the jobs that have only one history are only
> run once a month, and I have jobs that run daily - they
> have all the job history up to a month.
> Alex
> history
> is
> remain.
> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
> confers no rights.|||Thanks Jasper. This is exactly the problem, and your
suggested solution is spot on.
Alex
>--Original Message--
>The trouble is that if you have a job that runs very
often e.g once every
>minute, it can quickly eat up the 1000 rows that is the
default job history
>log size. This setting applies to the server so even if
the job history rows
>per job is 100, it will not honour this if the max
history log size >1000.
>Thus it might be worth lowering the rows per job and
increasing the max log
>size to find the balance that works for you.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:2d9401c40075$21391820$a601280a@.phx.gbl...
the
historic
history
Manager)
System?
and
>
>.
>
In enterprise manager -> management-> jobs -> view history
I could normally see the historic runs of the jobs.
I have a server, for some reason, only hold one historic
record of each job. Each time a job is run the history is
then refreshed and delete with only the latest job remain.
Where can I set in Enterprise Manager so I could adjust
the amount of the history held for the jobs?
Thanks
AlexAlex Au wrote:
> Please could someone enlight me.
> In enterprise manager -> management-> jobs -> view history
> I could normally see the historic runs of the jobs.
> I have a server, for some reason, only hold one historic
> record of each job. Each time a job is run the history is
> then refreshed and delete with only the latest job remain.
See How to resize the job history log (Enterprise Manager)
http://msdn.microsoft.com/library/d...>
aem_8xpj.asp
Why not create Your Own SQL Server Job Management System?
http://www.sql-server-performance.com/rd_jobs.asp
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Sebastian
Thanks for this. I have checked and found that the Job
agent setting no different from other servers. I think the
real issue seem to be in the time the job history are
kept.. All the jobs that have only one history are only
run once a month, and I have jobs that run daily - they
have all the job history up to a month.
Alex
>--Original Message--
>Alex Au wrote:
>
history
is
remain.
>
>See How to resize the job history log (Enterprise Manager)
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>Why not create Your Own SQL Server Job Management System?
>http://www.sql-server-performance.com/rd_jobs.asp
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||The trouble is that if you have a job that runs very often e.g once every
minute, it can quickly eat up the 1000 rows that is the default job history
log size. This setting applies to the server so even if the job history rows
per job is 100, it will not honour this if the max history log size >1000.
Thus it might be worth lowering the rows per job and increasing the max log
size to find the balance that works for you.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2d9401c40075$21391820$a601280a@.phx.gbl...
> Sebastian
> Thanks for this. I have checked and found that the Job
> agent setting no different from other servers. I think the
> real issue seem to be in the time the job history are
> kept.. All the jobs that have only one history are only
> run once a month, and I have jobs that run daily - they
> have all the job history up to a month.
> Alex
> history
> is
> remain.
> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
> confers no rights.|||Thanks Jasper. This is exactly the problem, and your
suggested solution is spot on.
Alex
>--Original Message--
>The trouble is that if you have a job that runs very
often e.g once every
>minute, it can quickly eat up the 1000 rows that is the
default job history
>log size. This setting applies to the server so even if
the job history rows
>per job is 100, it will not honour this if the max
history log size >1000.
>Thus it might be worth lowering the rows per job and
increasing the max log
>size to find the balance that works for you.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:2d9401c40075$21391820$a601280a@.phx.gbl...
the
historic
history
Manager)
System?
and
>
>.
>
Question on Job history
Please could someone enlight me.
In enterprise manager -> management-> jobs -> view history
I could normally see the historic runs of the jobs.
I have a server, for some reason, only hold one historic
record of each job. Each time a job is run the history is
then refreshed and delete with only the latest job remain.
Where can I set in Enterprise Manager so I could adjust
the amount of the history held for the jobs?
Thanks
AlexAlex Au wrote:
> Please could someone enlight me.
> In enterprise manager -> management-> jobs -> view history
> I could normally see the historic runs of the jobs.
> I have a server, for some reason, only hold one historic
> record of each job. Each time a job is run the history is
> then refreshed and delete with only the latest job remain.
See How to resize the job history log (Enterprise Manager)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_automaem_8xpj.asp
Why not create Your Own SQL Server Job Management System?
http://www.sql-server-performance.com/rd_jobs.asp
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Sebastian
Thanks for this. I have checked and found that the Job
agent setting no different from other servers. I think the
real issue seem to be in the time the job history are
kept.. All the jobs that have only one history are only
run once a month, and I have jobs that run daily - they
have all the job history up to a month.
Alex
>--Original Message--
>Alex Au wrote:
>> Please could someone enlight me.
>> In enterprise manager -> management-> jobs -> view
history
>> I could normally see the historic runs of the jobs.
>> I have a server, for some reason, only hold one historic
>> record of each job. Each time a job is run the history
is
>> then refreshed and delete with only the latest job
remain.
>
>See How to resize the job history log (Enterprise Manager)
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>Why not create Your Own SQL Server Job Management System?
>http://www.sql-server-performance.com/rd_jobs.asp
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||The trouble is that if you have a job that runs very often e.g once every
minute, it can quickly eat up the 1000 rows that is the default job history
log size. This setting applies to the server so even if the job history rows
per job is 100, it will not honour this if the max history log size >1000.
Thus it might be worth lowering the rows per job and increasing the max log
size to find the balance that works for you.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2d9401c40075$21391820$a601280a@.phx.gbl...
> Sebastian
> Thanks for this. I have checked and found that the Job
> agent setting no different from other servers. I think the
> real issue seem to be in the time the job history are
> kept.. All the jobs that have only one history are only
> run once a month, and I have jobs that run daily - they
> have all the job history up to a month.
> Alex
> >--Original Message--
> >Alex Au wrote:
> >
> >> Please could someone enlight me.
> >>
> >> In enterprise manager -> management-> jobs -> view
> history
> >> I could normally see the historic runs of the jobs.
> >>
> >> I have a server, for some reason, only hold one historic
> >> record of each job. Each time a job is run the history
> is
> >> then refreshed and delete with only the latest job
> remain.
> >
> >
> >See How to resize the job history log (Enterprise Manager)
> >http://msdn.microsoft.com/library/default.asp?
> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
> >
> >Why not create Your Own SQL Server Job Management System?
> >http://www.sql-server-performance.com/rd_jobs.asp
> >
> >sincerely,
> >--
> >Sebastian K. Zaklada
> >Skilled Software
> >http://www.skilledsoftware.com
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >.
> >|||Thanks Jasper. This is exactly the problem, and your
suggested solution is spot on.
Alex
>--Original Message--
>The trouble is that if you have a job that runs very
often e.g once every
>minute, it can quickly eat up the 1000 rows that is the
default job history
>log size. This setting applies to the server so even if
the job history rows
>per job is 100, it will not honour this if the max
history log size >1000.
>Thus it might be worth lowering the rows per job and
increasing the max log
>size to find the balance that works for you.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:2d9401c40075$21391820$a601280a@.phx.gbl...
>> Sebastian
>> Thanks for this. I have checked and found that the Job
>> agent setting no different from other servers. I think
the
>> real issue seem to be in the time the job history are
>> kept.. All the jobs that have only one history are only
>> run once a month, and I have jobs that run daily - they
>> have all the job history up to a month.
>> Alex
>> >--Original Message--
>> >Alex Au wrote:
>> >
>> >> Please could someone enlight me.
>> >>
>> >> In enterprise manager -> management-> jobs -> view
>> history
>> >> I could normally see the historic runs of the jobs.
>> >>
>> >> I have a server, for some reason, only hold one
historic
>> >> record of each job. Each time a job is run the
history
>> is
>> >> then refreshed and delete with only the latest job
>> remain.
>> >
>> >
>> >See How to resize the job history log (Enterprise
Manager)
>> >http://msdn.microsoft.com/library/default.asp?
>> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>> >
>> >Why not create Your Own SQL Server Job Management
System?
>> >http://www.sql-server-performance.com/rd_jobs.asp
>> >
>> >sincerely,
>> >--
>> >Sebastian K. Zaklada
>> >Skilled Software
>> >http://www.skilledsoftware.com
>> >This posting is provided "AS IS" with no warranties,
and
>> confers no rights.
>> >
>> >
>> >.
>> >
>
>.
>
In enterprise manager -> management-> jobs -> view history
I could normally see the historic runs of the jobs.
I have a server, for some reason, only hold one historic
record of each job. Each time a job is run the history is
then refreshed and delete with only the latest job remain.
Where can I set in Enterprise Manager so I could adjust
the amount of the history held for the jobs?
Thanks
AlexAlex Au wrote:
> Please could someone enlight me.
> In enterprise manager -> management-> jobs -> view history
> I could normally see the historic runs of the jobs.
> I have a server, for some reason, only hold one historic
> record of each job. Each time a job is run the history is
> then refreshed and delete with only the latest job remain.
See How to resize the job history log (Enterprise Manager)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_automaem_8xpj.asp
Why not create Your Own SQL Server Job Management System?
http://www.sql-server-performance.com/rd_jobs.asp
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Sebastian
Thanks for this. I have checked and found that the Job
agent setting no different from other servers. I think the
real issue seem to be in the time the job history are
kept.. All the jobs that have only one history are only
run once a month, and I have jobs that run daily - they
have all the job history up to a month.
Alex
>--Original Message--
>Alex Au wrote:
>> Please could someone enlight me.
>> In enterprise manager -> management-> jobs -> view
history
>> I could normally see the historic runs of the jobs.
>> I have a server, for some reason, only hold one historic
>> record of each job. Each time a job is run the history
is
>> then refreshed and delete with only the latest job
remain.
>
>See How to resize the job history log (Enterprise Manager)
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>Why not create Your Own SQL Server Job Management System?
>http://www.sql-server-performance.com/rd_jobs.asp
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||The trouble is that if you have a job that runs very often e.g once every
minute, it can quickly eat up the 1000 rows that is the default job history
log size. This setting applies to the server so even if the job history rows
per job is 100, it will not honour this if the max history log size >1000.
Thus it might be worth lowering the rows per job and increasing the max log
size to find the balance that works for you.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2d9401c40075$21391820$a601280a@.phx.gbl...
> Sebastian
> Thanks for this. I have checked and found that the Job
> agent setting no different from other servers. I think the
> real issue seem to be in the time the job history are
> kept.. All the jobs that have only one history are only
> run once a month, and I have jobs that run daily - they
> have all the job history up to a month.
> Alex
> >--Original Message--
> >Alex Au wrote:
> >
> >> Please could someone enlight me.
> >>
> >> In enterprise manager -> management-> jobs -> view
> history
> >> I could normally see the historic runs of the jobs.
> >>
> >> I have a server, for some reason, only hold one historic
> >> record of each job. Each time a job is run the history
> is
> >> then refreshed and delete with only the latest job
> remain.
> >
> >
> >See How to resize the job history log (Enterprise Manager)
> >http://msdn.microsoft.com/library/default.asp?
> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
> >
> >Why not create Your Own SQL Server Job Management System?
> >http://www.sql-server-performance.com/rd_jobs.asp
> >
> >sincerely,
> >--
> >Sebastian K. Zaklada
> >Skilled Software
> >http://www.skilledsoftware.com
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >.
> >|||Thanks Jasper. This is exactly the problem, and your
suggested solution is spot on.
Alex
>--Original Message--
>The trouble is that if you have a job that runs very
often e.g once every
>minute, it can quickly eat up the 1000 rows that is the
default job history
>log size. This setting applies to the server so even if
the job history rows
>per job is 100, it will not honour this if the max
history log size >1000.
>Thus it might be worth lowering the rows per job and
increasing the max log
>size to find the balance that works for you.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:2d9401c40075$21391820$a601280a@.phx.gbl...
>> Sebastian
>> Thanks for this. I have checked and found that the Job
>> agent setting no different from other servers. I think
the
>> real issue seem to be in the time the job history are
>> kept.. All the jobs that have only one history are only
>> run once a month, and I have jobs that run daily - they
>> have all the job history up to a month.
>> Alex
>> >--Original Message--
>> >Alex Au wrote:
>> >
>> >> Please could someone enlight me.
>> >>
>> >> In enterprise manager -> management-> jobs -> view
>> history
>> >> I could normally see the historic runs of the jobs.
>> >>
>> >> I have a server, for some reason, only hold one
historic
>> >> record of each job. Each time a job is run the
history
>> is
>> >> then refreshed and delete with only the latest job
>> remain.
>> >
>> >
>> >See How to resize the job history log (Enterprise
Manager)
>> >http://msdn.microsoft.com/library/default.asp?
>> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>> >
>> >Why not create Your Own SQL Server Job Management
System?
>> >http://www.sql-server-performance.com/rd_jobs.asp
>> >
>> >sincerely,
>> >--
>> >Sebastian K. Zaklada
>> >Skilled Software
>> >http://www.skilledsoftware.com
>> >This posting is provided "AS IS" with no warranties,
and
>> confers no rights.
>> >
>> >
>> >.
>> >
>
>.
>
Saturday, February 25, 2012
Question on Changing Jobs in SQL Server 2000
We have a bunch of databases on this SQL Server 2000 and for each
database we pretty much have the same kind of job running daily and
weekly. We are running out of disk space where we used to normally
backup the databases so we now have a new drive which will be used only
for backups so I need to change all my jobs to backup the databases to
the new drive. I can do that manually by going into each job to change
the drive path, but I was wondering if there was a way to update the
system table so that I did not have to manually change all my jobs.
Any help, ideas in this regard will be greatly appreciated.
ThanksHi
This is where having devices would make the task easier! But you can script
the jobs from Enterprise manager and then globally edit the file created.
John
"shub" wrote:
> We have a bunch of databases on this SQL Server 2000 and for each
> database we pretty much have the same kind of job running daily and
> weekly. We are running out of disk space where we used to normally
> backup the databases so we now have a new drive which will be used only
> for backups so I need to change all my jobs to backup the databases to
> the new drive. I can do that manually by going into each job to change
> the drive path, but I was wondering if there was a way to update the
> system table so that I did not have to manually change all my jobs.
> Any help, ideas in this regard will be greatly appreciated.
> Thanks
>|||John
Thanks for your response. Wouldnt the script drop the existing job and
create a brand new one which would cause me to lose all my job history?
Is there a way to get around that?
Thanks|||Hi
Yes it would, the jobs would have different Ids when re-created so you would
have to export everything before doing the scripting. Another reason for
using devices.
John
"shub" wrote:
> John
> Thanks for your response. Wouldnt the script drop the existing job and
> create a brand new one which would cause me to lose all my job history?
> Is there a way to get around that?
> Thanks
>|||John,
If we had devices in place would't we still need to change tha path off
all the devices that we set up for all the different databases? Also
can you set up devices if the physical location of the back up files
are in different computers in the network, basically does it support
UNC? I will look it up myself, but I would sure appreciate your input
as well.
Thanks again|||Hi
If you need to change the job to make it use a device it will not change the
problems of loosing the history, only make it more flexible in the future.
You should only be keeping a certain amount of history as this information
will bloat your msdb, if you need to retain this for a prolonged period then
you may want to put into place a system that will copy it elsewhere.
Devices can use UNC paths, there is an example of sp_adddumpdevice in books
online that shows exactly this. If you are backing up to another machine it
is worth considering a dedicated (1GB) subnet and adding extra cards to
improve performance.
John
"shub" wrote:
> John,
> If we had devices in place would't we still need to change tha path off
> all the devices that we set up for all the different databases? Also
> can you set up devices if the physical location of the back up files
> are in different computers in the network, basically does it support
> UNC? I will look it up myself, but I would sure appreciate your input
> as well.
> Thanks again
>|||I believe when all our jobs were created originally they were all
created by The maintenance plan wizard and I don't see you have an
option of backing up databases to devices.
Maybe in the near future we need to look at redoing all our jobs to use
the devices.
Thank you for all your help.
database we pretty much have the same kind of job running daily and
weekly. We are running out of disk space where we used to normally
backup the databases so we now have a new drive which will be used only
for backups so I need to change all my jobs to backup the databases to
the new drive. I can do that manually by going into each job to change
the drive path, but I was wondering if there was a way to update the
system table so that I did not have to manually change all my jobs.
Any help, ideas in this regard will be greatly appreciated.
ThanksHi
This is where having devices would make the task easier! But you can script
the jobs from Enterprise manager and then globally edit the file created.
John
"shub" wrote:
> We have a bunch of databases on this SQL Server 2000 and for each
> database we pretty much have the same kind of job running daily and
> weekly. We are running out of disk space where we used to normally
> backup the databases so we now have a new drive which will be used only
> for backups so I need to change all my jobs to backup the databases to
> the new drive. I can do that manually by going into each job to change
> the drive path, but I was wondering if there was a way to update the
> system table so that I did not have to manually change all my jobs.
> Any help, ideas in this regard will be greatly appreciated.
> Thanks
>|||John
Thanks for your response. Wouldnt the script drop the existing job and
create a brand new one which would cause me to lose all my job history?
Is there a way to get around that?
Thanks|||Hi
Yes it would, the jobs would have different Ids when re-created so you would
have to export everything before doing the scripting. Another reason for
using devices.
John
"shub" wrote:
> John
> Thanks for your response. Wouldnt the script drop the existing job and
> create a brand new one which would cause me to lose all my job history?
> Is there a way to get around that?
> Thanks
>|||John,
If we had devices in place would't we still need to change tha path off
all the devices that we set up for all the different databases? Also
can you set up devices if the physical location of the back up files
are in different computers in the network, basically does it support
UNC? I will look it up myself, but I would sure appreciate your input
as well.
Thanks again|||Hi
If you need to change the job to make it use a device it will not change the
problems of loosing the history, only make it more flexible in the future.
You should only be keeping a certain amount of history as this information
will bloat your msdb, if you need to retain this for a prolonged period then
you may want to put into place a system that will copy it elsewhere.
Devices can use UNC paths, there is an example of sp_adddumpdevice in books
online that shows exactly this. If you are backing up to another machine it
is worth considering a dedicated (1GB) subnet and adding extra cards to
improve performance.
John
"shub" wrote:
> John,
> If we had devices in place would't we still need to change tha path off
> all the devices that we set up for all the different databases? Also
> can you set up devices if the physical location of the back up files
> are in different computers in the network, basically does it support
> UNC? I will look it up myself, but I would sure appreciate your input
> as well.
> Thanks again
>|||I believe when all our jobs were created originally they were all
created by The maintenance plan wizard and I don't see you have an
option of backing up databases to devices.
Maybe in the near future we need to look at redoing all our jobs to use
the devices.
Thank you for all your help.
Question on Changing Jobs in SQL Server 2000
We have a bunch of databases on this SQL Server 2000 and for each
database we pretty much have the same kind of job running daily and
weekly. We are running out of disk space where we used to normally
backup the databases so we now have a new drive which will be used only
for backups so I need to change all my jobs to backup the databases to
the new drive. I can do that manually by going into each job to change
the drive path, but I was wondering if there was a way to update the
system table so that I did not have to manually change all my jobs.
Any help, ideas in this regard will be greatly appreciated.
ThanksHi
This is where having devices would make the task easier! But you can script
the jobs from Enterprise manager and then globally edit the file created.
John
"shub" wrote:
> We have a bunch of databases on this SQL Server 2000 and for each
> database we pretty much have the same kind of job running daily and
> weekly. We are running out of disk space where we used to normally
> backup the databases so we now have a new drive which will be used only
> for backups so I need to change all my jobs to backup the databases to
> the new drive. I can do that manually by going into each job to change
> the drive path, but I was wondering if there was a way to update the
> system table so that I did not have to manually change all my jobs.
> Any help, ideas in this regard will be greatly appreciated.
> Thanks
>|||John
Thanks for your response. Wouldnt the script drop the existing job and
create a brand new one which would cause me to lose all my job history?
Is there a way to get around that?
Thanks|||Hi
Yes it would, the jobs would have different Ids when re-created so you would
have to export everything before doing the scripting. Another reason for
using devices.
John
"shub" wrote:
> John
> Thanks for your response. Wouldnt the script drop the existing job and
> create a brand new one which would cause me to lose all my job history?
> Is there a way to get around that?
> Thanks
>|||John,
If we had devices in place would't we still need to change tha path off
all the devices that we set up for all the different databases? Also
can you set up devices if the physical location of the back up files
are in different computers in the network, basically does it support
UNC? I will look it up myself, but I would sure appreciate your input
as well.
Thanks again|||Hi
If you need to change the job to make it use a device it will not change the
problems of loosing the history, only make it more flexible in the future.
You should only be keeping a certain amount of history as this information
will bloat your msdb, if you need to retain this for a prolonged period then
you may want to put into place a system that will copy it elsewhere.
Devices can use UNC paths, there is an example of sp_adddumpdevice in books
online that shows exactly this. If you are backing up to another machine it
is worth considering a dedicated (1GB) subnet and adding extra cards to
improve performance.
John
"shub" wrote:
> John,
> If we had devices in place would't we still need to change tha path off
> all the devices that we set up for all the different databases? Also
> can you set up devices if the physical location of the back up files
> are in different computers in the network, basically does it support
> UNC? I will look it up myself, but I would sure appreciate your input
> as well.
> Thanks again
>|||I believe when all our jobs were created originally they were all
created by The maintenance plan wizard and I don't see you have an
option of backing up databases to devices.
Maybe in the near future we need to look at redoing all our jobs to use
the devices.
Thank you for all your help.
database we pretty much have the same kind of job running daily and
weekly. We are running out of disk space where we used to normally
backup the databases so we now have a new drive which will be used only
for backups so I need to change all my jobs to backup the databases to
the new drive. I can do that manually by going into each job to change
the drive path, but I was wondering if there was a way to update the
system table so that I did not have to manually change all my jobs.
Any help, ideas in this regard will be greatly appreciated.
ThanksHi
This is where having devices would make the task easier! But you can script
the jobs from Enterprise manager and then globally edit the file created.
John
"shub" wrote:
> We have a bunch of databases on this SQL Server 2000 and for each
> database we pretty much have the same kind of job running daily and
> weekly. We are running out of disk space where we used to normally
> backup the databases so we now have a new drive which will be used only
> for backups so I need to change all my jobs to backup the databases to
> the new drive. I can do that manually by going into each job to change
> the drive path, but I was wondering if there was a way to update the
> system table so that I did not have to manually change all my jobs.
> Any help, ideas in this regard will be greatly appreciated.
> Thanks
>|||John
Thanks for your response. Wouldnt the script drop the existing job and
create a brand new one which would cause me to lose all my job history?
Is there a way to get around that?
Thanks|||Hi
Yes it would, the jobs would have different Ids when re-created so you would
have to export everything before doing the scripting. Another reason for
using devices.
John
"shub" wrote:
> John
> Thanks for your response. Wouldnt the script drop the existing job and
> create a brand new one which would cause me to lose all my job history?
> Is there a way to get around that?
> Thanks
>|||John,
If we had devices in place would't we still need to change tha path off
all the devices that we set up for all the different databases? Also
can you set up devices if the physical location of the back up files
are in different computers in the network, basically does it support
UNC? I will look it up myself, but I would sure appreciate your input
as well.
Thanks again|||Hi
If you need to change the job to make it use a device it will not change the
problems of loosing the history, only make it more flexible in the future.
You should only be keeping a certain amount of history as this information
will bloat your msdb, if you need to retain this for a prolonged period then
you may want to put into place a system that will copy it elsewhere.
Devices can use UNC paths, there is an example of sp_adddumpdevice in books
online that shows exactly this. If you are backing up to another machine it
is worth considering a dedicated (1GB) subnet and adding extra cards to
improve performance.
John
"shub" wrote:
> John,
> If we had devices in place would't we still need to change tha path off
> all the devices that we set up for all the different databases? Also
> can you set up devices if the physical location of the back up files
> are in different computers in the network, basically does it support
> UNC? I will look it up myself, but I would sure appreciate your input
> as well.
> Thanks again
>|||I believe when all our jobs were created originally they were all
created by The maintenance plan wizard and I don't see you have an
option of backing up databases to devices.
Maybe in the near future we need to look at redoing all our jobs to use
the devices.
Thank you for all your help.
Monday, February 20, 2012
Question of SQLAgentMail and SQL Mail
Hi,
I need monitoring scheduling jobs, alerts and database
maintenance from daily manually checks to automation. If
any of them failed while execute, it should be
automatically email to operator. I knew it can be done by
configuring SQLAgentMail and SQL Mail, but how to
configuring? Any particular software need install such as
MS exchange server to the production SQL Server or other
requests? Also can anyone tell which link I should to
follow?
Thanks for all the help!
-Jenny
http://www.aspfaq.com/2403
http://www.aspfaq.com/
(Reverse address to reply.)
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
|||Have a look at
SQL Mail
http://support.microsoft.com/default...;en-us;Q315886
http://support.microsoft.com/default...;en-us;Q321183
http://support.microsoft.com/default...;en-us;Q263556
http://support.microsoft.com/default...;en-us;Q311231
http://support.microsoft.com/default...;en-us;Q281293
Support Web Cast
http://support.microsoft.com/service...lurb091301.asp
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
I need monitoring scheduling jobs, alerts and database
maintenance from daily manually checks to automation. If
any of them failed while execute, it should be
automatically email to operator. I knew it can be done by
configuring SQLAgentMail and SQL Mail, but how to
configuring? Any particular software need install such as
MS exchange server to the production SQL Server or other
requests? Also can anyone tell which link I should to
follow?
Thanks for all the help!
-Jenny
http://www.aspfaq.com/2403
http://www.aspfaq.com/
(Reverse address to reply.)
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
|||Have a look at
SQL Mail
http://support.microsoft.com/default...;en-us;Q315886
http://support.microsoft.com/default...;en-us;Q321183
http://support.microsoft.com/default...;en-us;Q263556
http://support.microsoft.com/default...;en-us;Q311231
http://support.microsoft.com/default...;en-us;Q281293
Support Web Cast
http://support.microsoft.com/service...lurb091301.asp
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
Question of SQLAgentMail and SQL Mail
Hi,
I need monitoring scheduling jobs, alerts and database
maintenance from daily manually checks to automation. If
any of them failed while execute, it should be
automatically email to operator. I knew it can be done by
configuring SQLAgentMail and SQL Mail, but how to
configuring? Any particular software need install such as
MS exchange server to the production SQL Server or other
requests? Also can anyone tell which link I should to
follow?
Thanks for all the help!
-Jennyhttp://www.aspfaq.com/2403
http://www.aspfaq.com/
(Reverse address to reply.)
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>|||Have a look at
SQL Mail
http://support.microsoft.com/defaul...b;en-us;Q315886
http://support.microsoft.com/defaul...b;en-us;Q321183
http://support.microsoft.com/defaul...b;en-us;Q263556
http://support.microsoft.com/defaul...b;en-us;Q311231
http://support.microsoft.com/defaul...b;en-us;Q281293
Support Web Cast
]
HTH
Jasper Smith (SQL Server MVP)
[url]http://www.sqldbatips.com" target="_blank">http://support.microsoft.com/servic...sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
I need monitoring scheduling jobs, alerts and database
maintenance from daily manually checks to automation. If
any of them failed while execute, it should be
automatically email to operator. I knew it can be done by
configuring SQLAgentMail and SQL Mail, but how to
configuring? Any particular software need install such as
MS exchange server to the production SQL Server or other
requests? Also can anyone tell which link I should to
follow?
Thanks for all the help!
-Jennyhttp://www.aspfaq.com/2403
http://www.aspfaq.com/
(Reverse address to reply.)
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>|||Have a look at
SQL Mail
http://support.microsoft.com/defaul...b;en-us;Q315886
http://support.microsoft.com/defaul...b;en-us;Q321183
http://support.microsoft.com/defaul...b;en-us;Q263556
http://support.microsoft.com/defaul...b;en-us;Q311231
http://support.microsoft.com/defaul...b;en-us;Q281293
Support Web Cast
]
HTH
Jasper Smith (SQL Server MVP)
[url]http://www.sqldbatips.com" target="_blank">http://support.microsoft.com/servic...sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
Question of SQLAgentMail and SQL Mail
Hi,
I need monitoring scheduling jobs, alerts and database
maintenance from daily manually checks to automation. If
any of them failed while execute, it should be
automatically email to operator. I knew it can be done by
configuring SQLAgentMail and SQL Mail, but how to
configuring? Any particular software need install such as
MS exchange server to the production SQL Server or other
requests? Also can anyone tell which link I should to
follow?
Thanks for all the help!
-Jennyhttp://www.aspfaq.com/2403
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>|||Have a look at
SQL Mail
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315886
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q321183
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q263556
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311231
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281293
Support Web Cast
http://support.microsoft.com/servicedesks/webcasts/wc091301/wcblurb091301.asp
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
I need monitoring scheduling jobs, alerts and database
maintenance from daily manually checks to automation. If
any of them failed while execute, it should be
automatically email to operator. I knew it can be done by
configuring SQLAgentMail and SQL Mail, but how to
configuring? Any particular software need install such as
MS exchange server to the production SQL Server or other
requests? Also can anyone tell which link I should to
follow?
Thanks for all the help!
-Jennyhttp://www.aspfaq.com/2403
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>|||Have a look at
SQL Mail
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315886
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q321183
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q263556
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311231
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281293
Support Web Cast
http://support.microsoft.com/servicedesks/webcasts/wc091301/wcblurb091301.asp
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jenny" <jey@.iseoptions.com> wrote in message
news:601201c474df$220c7fb0$a401280a@.phx.gbl...
> Hi,
> I need monitoring scheduling jobs, alerts and database
> maintenance from daily manually checks to automation. If
> any of them failed while execute, it should be
> automatically email to operator. I knew it can be done by
> configuring SQLAgentMail and SQL Mail, but how to
> configuring? Any particular software need install such as
> MS exchange server to the production SQL Server or other
> requests? Also can anyone tell which link I should to
> follow?
> Thanks for all the help!
> -Jenny
>
Subscribe to:
Posts (Atom)