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.

job steps synchronous?

Quick question - if I have several steps in a job are they run one after the other or can there potentially be overlap. In one step I create a file and the subsequent step copies it, so I'm concerned that the first completes before the second begins
TIA
Frank SThey are sequental.
Bojidar Alexandrov|||Frank,
My experience is that it is no overlap.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Frank Spencer" <anonymous@.discussions.microsoft.com> wrote in message
news:C2E0F3EF-331D-49CF-A77E-ECCEF0710F32@.microsoft.com...
> Quick question - if I have several steps in a job are they run one after the other or can there potentially
be overlap. In one step I create a file and the subsequent step copies it, so I'm concerned that the first
completes before the second begins.
> TIA,
> Frank S

job steps synchronous?

Quick question - if I have several steps in a job are they run one after the
other or can there potentially be overlap. In one step I create a file and
the subsequent step copies it, so I'm concerned that the first completes bef
ore the second begins.
TIA,
Frank SThey are sequental.
Bojidar Alexandrov|||Frank,
My experience is that it is no overlap.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Frank Spencer" <anonymous@.discussions.microsoft.com> wrote in message
news:C2E0F3EF-331D-49CF-A77E-ECCEF0710F32@.microsoft.com...
> Quick question - if I have several steps in a job are they run one after the other
or can there potentially
be overlap. In one step I create a file and the subsequent step copies it, s
o I'm concerned that the first
completes before the second begins.
> TIA,
> Frank Ssql

job steps synchronous?

Quick question - if I have several steps in a job are they run one after the other or can there potentially be overlap. In one step I create a file and the subsequent step copies it, so I'm concerned that the first completes before the second begins.
TIA,
Frank S
They are sequental.
Bojidar Alexandrov
|||Frank,
My experience is that it is no overlap.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Frank Spencer" <anonymous@.discussions.microsoft.com> wrote in message
news:C2E0F3EF-331D-49CF-A77E-ECCEF0710F32@.microsoft.com...
> Quick question - if I have several steps in a job are they run one after the other or can there potentially
be overlap. In one step I create a file and the subsequent step copies it, so I'm concerned that the first
completes before the second begins.
> TIA,
> Frank S

Job SQL Limitation

Does anyone know what is the limitation on SQL Server job
SQL statement is ?. I am trying to create a job that has a
long SQL (Select) statement but it does not allow me to
put the whole statement (It truncates). What are the
alternatives (NOT DTS or QA)? These are more that 15
separeate SQL statements I need to schedule and get the
result in 1 file.
T.I.AWhen you say one file do you mean the output file for the job? If so why
not place these in stored procedures and simply run them?
Andrew J. Kelly SQL MVP
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:210b01c50239$2df26960$a401280a@.phx.gbl...
> Does anyone know what is the limitation on SQL Server job
> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives (NOT DTS or QA)? These are more that 15
> separeate SQL statements I need to schedule and get the
> result in 1 file.
> T.I.A|||> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives
Put your T-SQL code in a stored procedure?
http://www.aspfaq.com/
(Reverse address to reply.)|||If you cannot or do not want to create a stored procedure (for whatever
reason) I suggest you save your T-SQL to a file on the local hard drive.
You can use osql.exe to execute the script file within the job step.
Keith
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:210b01c50239$2df26960$a401280a@.phx.gbl...
> Does anyone know what is the limitation on SQL Server job
> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives (NOT DTS or QA)? These are more that 15
> separeate SQL statements I need to schedule and get the
> result in 1 file.
> T.I.A|||Just to add...the limit is 3200 characters.
-Sue
On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
<anonymous@.discussions.microsoft.com> wrote:

>Does anyone know what is the limitation on SQL Server job
>SQL statement is ?. I am trying to create a job that has a
>long SQL (Select) statement but it does not allow me to
>put the whole statement (It truncates). What are the
>alternatives (NOT DTS or QA)? These are more that 15
>separeate SQL statements I need to schedule and get the
>result in 1 file.
>T.I.A|||Thanks to all.........
I will use SP.......

>--Original Message--
has a[vbcol=seagreen]
>Put your T-SQL code in a stored procedure?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||Although, I put the statements into a SP, I don't get the
same output in Scheduled job output as I get out of the QA
(I like to get it as it is in QA output).
Thanks.

>--Original Message--
has a[vbcol=seagreen]
>Put your T-SQL code in a stored procedure?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||But EM might be more restrictive then 3200 characters. I recall a case a lon
g time ago when I tested
it, and conclusion was that if you need more than what EM allows, you need t
o add the jobsteps using
sp_add_jobstep.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:djeav0140graejhho9kee8u1qkd68olvgf@.
4ax.com...
> Just to add...the limit is 3200 characters.
> -Sue
> On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
> <anonymous@.discussions.microsoft.com> wrote:
>
>|||I have 1 Select statement that is 3750 characters which
does not go into any job steps.........

>--Original Message--
>But EM might be more restrictive then 3200 characters. I
recall a case a long time ago when I tested
>it, and conclusion was that if you need more than what EM
allows, you need to add the jobsteps using
>sp_add_jobstep.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>http://www.sqlug.se/
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:djeav0140graejhho9kee8u1qkd68olvgf@.
4ax.com...
job[vbcol=seagreen]
has a[vbcol=seagreen]
>
>.
>|||If you are > 3200 characters, you cannot have it directly in the jobstep reg
ardless of whether you
are using EM or call sp_add_jobstep directly. Use any of the other suggested
methods (put it in a
stored procedure, or use CmdExec jobstep which calls OSQL.EXE with an inputf
ile).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:062b01c502e5$e2bc1330$a601280a@.phx.gbl...[vbcol=seagreen]
>I have 1 Select statement that is 3750 characters which
> does not go into any job steps.........
>
> recall a case a long time ago when I tested
> allows, you need to add the jobsteps using
> job
> has a

Job SQL Limitation

Does anyone know what is the limitation on SQL Server job
SQL statement is ?. I am trying to create a job that has a
long SQL (Select) statement but it does not allow me to
put the whole statement (It truncates). What are the
alternatives (NOT DTS or QA)? These are more that 15
separeate SQL statements I need to schedule and get the
result in 1 file.
T.I.AWhen you say one file do you mean the output file for the job? If so why
not place these in stored procedures and simply run them?
--
Andrew J. Kelly SQL MVP
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:210b01c50239$2df26960$a401280a@.phx.gbl...
> Does anyone know what is the limitation on SQL Server job
> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives (NOT DTS or QA)? These are more that 15
> separeate SQL statements I need to schedule and get the
> result in 1 file.
> T.I.A|||> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives
Put your T-SQL code in a stored procedure?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||If you cannot or do not want to create a stored procedure (for whatever
reason) I suggest you save your T-SQL to a file on the local hard drive.
You can use osql.exe to execute the script file within the job step.
--
Keith
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:210b01c50239$2df26960$a401280a@.phx.gbl...
> Does anyone know what is the limitation on SQL Server job
> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives (NOT DTS or QA)? These are more that 15
> separeate SQL statements I need to schedule and get the
> result in 1 file.
> T.I.A|||Just to add...the limit is 3200 characters.
-Sue
On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
<anonymous@.discussions.microsoft.com> wrote:
>Does anyone know what is the limitation on SQL Server job
>SQL statement is ?. I am trying to create a job that has a
>long SQL (Select) statement but it does not allow me to
>put the whole statement (It truncates). What are the
>alternatives (NOT DTS or QA)? These are more that 15
>separeate SQL statements I need to schedule and get the
>result in 1 file.
>T.I.A|||Thanks to all.........
I will use SP.......
>--Original Message--
>> SQL statement is ?. I am trying to create a job that
has a
>> long SQL (Select) statement but it does not allow me to
>> put the whole statement (It truncates). What are the
>> alternatives
>Put your T-SQL code in a stored procedure?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||Although, I put the statements into a SP, I don't get the
same output in Scheduled job output as I get out of the QA
(I like to get it as it is in QA output).
Thanks.
>--Original Message--
>> SQL statement is ?. I am trying to create a job that
has a
>> long SQL (Select) statement but it does not allow me to
>> put the whole statement (It truncates). What are the
>> alternatives
>Put your T-SQL code in a stored procedure?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||But EM might be more restrictive then 3200 characters. I recall a case a long time ago when I tested
it, and conclusion was that if you need more than what EM allows, you need to add the jobsteps using
sp_add_jobstep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:djeav0140graejhho9kee8u1qkd68olvgf@.4ax.com...
> Just to add...the limit is 3200 characters.
> -Sue
> On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
> <anonymous@.discussions.microsoft.com> wrote:
>>Does anyone know what is the limitation on SQL Server job
>>SQL statement is ?. I am trying to create a job that has a
>>long SQL (Select) statement but it does not allow me to
>>put the whole statement (It truncates). What are the
>>alternatives (NOT DTS or QA)? These are more that 15
>>separeate SQL statements I need to schedule and get the
>>result in 1 file.
>>T.I.A
>|||I have 1 Select statement that is 3750 characters which
does not go into any job steps.........
>--Original Message--
>But EM might be more restrictive then 3200 characters. I
recall a case a long time ago when I tested
>it, and conclusion was that if you need more than what EM
allows, you need to add the jobsteps using
>sp_add_jobstep.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>http://www.sqlug.se/
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:djeav0140graejhho9kee8u1qkd68olvgf@.4ax.com...
>> Just to add...the limit is 3200 characters.
>> -Sue
>> On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Does anyone know what is the limitation on SQL Server
job
>>SQL statement is ?. I am trying to create a job that
has a
>>long SQL (Select) statement but it does not allow me to
>>put the whole statement (It truncates). What are the
>>alternatives (NOT DTS or QA)? These are more that 15
>>separeate SQL statements I need to schedule and get the
>>result in 1 file.
>>T.I.A
>
>.
>|||If you are > 3200 characters, you cannot have it directly in the jobstep regardless of whether you
are using EM or call sp_add_jobstep directly. Use any of the other suggested methods (put it in a
stored procedure, or use CmdExec jobstep which calls OSQL.EXE with an inputfile).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:062b01c502e5$e2bc1330$a601280a@.phx.gbl...
>I have 1 Select statement that is 3750 characters which
> does not go into any job steps.........
>
>>--Original Message--
>>But EM might be more restrictive then 3200 characters. I
> recall a case a long time ago when I tested
>>it, and conclusion was that if you need more than what EM
> allows, you need to add the jobsteps using
>>sp_add_jobstep.
>>--
>>Tibor Karaszi, SQL Server MVP
>>http://www.karaszi.com/sqlserver/default.asp
>>http://www.solidqualitylearning.com/
>>http://www.sqlug.se/
>>
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:djeav0140graejhho9kee8u1qkd68olvgf@.4ax.com...
>> Just to add...the limit is 3200 characters.
>> -Sue
>> On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Does anyone know what is the limitation on SQL Server
> job
>>SQL statement is ?. I am trying to create a job that
> has a
>>long SQL (Select) statement but it does not allow me to
>>put the whole statement (It truncates). What are the
>>alternatives (NOT DTS or QA)? These are more that 15
>>separeate SQL statements I need to schedule and get the
>>result in 1 file.
>>T.I.A
>>
>>.|||But my output is not the same as it is in the QA.
>--Original Message--
>If you are > 3200 characters, you cannot have it directly
in the jobstep regardless of whether you
>are using EM or call sp_add_jobstep directly. Use any of
the other suggested methods (put it in a
>stored procedure, or use CmdExec jobstep which calls
OSQL.EXE with an inputfile).
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>http://www.sqlug.se/
>
>"Ken" <anonymous@.discussions.microsoft.com> wrote in
message
>news:062b01c502e5$e2bc1330$a601280a@.phx.gbl...
>>I have 1 Select statement that is 3750 characters which
>> does not go into any job steps.........
>>
>>--Original Message--
>>But EM might be more restrictive then 3200 characters. I
>> recall a case a long time ago when I tested
>>it, and conclusion was that if you need more than what
EM
>> allows, you need to add the jobsteps using
>>sp_add_jobstep.
>>--
>>Tibor Karaszi, SQL Server MVP
>>http://www.karaszi.com/sqlserver/default.asp
>>http://www.solidqualitylearning.com/
>>http://www.sqlug.se/
>>
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:djeav0140graejhho9kee8u1qkd68olvgf@.4ax.com...
>> Just to add...the limit is 3200 characters.
>> -Sue
>> On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Does anyone know what is the limitation on SQL Server
>> job
>>SQL statement is ?. I am trying to create a job that
>> has a
>>long SQL (Select) statement but it does not allow me
to
>>put the whole statement (It truncates). What are the
>>alternatives (NOT DTS or QA)? These are more that 15
>>separeate SQL statements I need to schedule and get
the
>>result in 1 file.
>>T.I.A
>>
>>.
>
>.
>|||In which way does it differ? And where do you see this output?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:1c8001c502ee$1e5e3690$a501280a@.phx.gbl...
> But my output is not the same as it is in the QA.
>
>>--Original Message--
>>If you are > 3200 characters, you cannot have it directly
> in the jobstep regardless of whether you
>>are using EM or call sp_add_jobstep directly. Use any of
> the other suggested methods (put it in a
>>stored procedure, or use CmdExec jobstep which calls
> OSQL.EXE with an inputfile).
>>--
>>Tibor Karaszi, SQL Server MVP
>>http://www.karaszi.com/sqlserver/default.asp
>>http://www.solidqualitylearning.com/
>>http://www.sqlug.se/
>>
>>"Ken" <anonymous@.discussions.microsoft.com> wrote in
> message
>>news:062b01c502e5$e2bc1330$a601280a@.phx.gbl...
>>I have 1 Select statement that is 3750 characters which
>> does not go into any job steps.........
>>
>>--Original Message--
>>But EM might be more restrictive then 3200 characters. I
>> recall a case a long time ago when I tested
>>it, and conclusion was that if you need more than what
> EM
>> allows, you need to add the jobsteps using
>>sp_add_jobstep.
>>--
>>Tibor Karaszi, SQL Server MVP
>>http://www.karaszi.com/sqlserver/default.asp
>>http://www.solidqualitylearning.com/
>>http://www.sqlug.se/
>>
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:djeav0140graejhho9kee8u1qkd68olvgf@.4ax.com...
>> Just to add...the limit is 3200 characters.
>> -Sue
>> On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Does anyone know what is the limitation on SQL Server
>> job
>>SQL statement is ?. I am trying to create a job that
>> has a
>>long SQL (Select) statement but it does not allow me
> to
>>put the whole statement (It truncates). What are the
>>alternatives (NOT DTS or QA)? These are more that 15
>>separeate SQL statements I need to schedule and get
> the
>>result in 1 file.
>>T.I.A
>>
>>.
>>
>>.

Job SQL Limitation

Does anyone know what is the limitation on SQL Server job
SQL statement is ?. I am trying to create a job that has a
long SQL (Select) statement but it does not allow me to
put the whole statement (It truncates). What are the
alternatives (NOT DTS or QA)? These are more that 15
separeate SQL statements I need to schedule and get the
result in 1 file.
T.I.A
When you say one file do you mean the output file for the job? If so why
not place these in stored procedures and simply run them?
Andrew J. Kelly SQL MVP
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:210b01c50239$2df26960$a401280a@.phx.gbl...
> Does anyone know what is the limitation on SQL Server job
> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives (NOT DTS or QA)? These are more that 15
> separeate SQL statements I need to schedule and get the
> result in 1 file.
> T.I.A
|||> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives
Put your T-SQL code in a stored procedure?
http://www.aspfaq.com/
(Reverse address to reply.)
|||If you cannot or do not want to create a stored procedure (for whatever
reason) I suggest you save your T-SQL to a file on the local hard drive.
You can use osql.exe to execute the script file within the job step.
Keith
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:210b01c50239$2df26960$a401280a@.phx.gbl...
> Does anyone know what is the limitation on SQL Server job
> SQL statement is ?. I am trying to create a job that has a
> long SQL (Select) statement but it does not allow me to
> put the whole statement (It truncates). What are the
> alternatives (NOT DTS or QA)? These are more that 15
> separeate SQL statements I need to schedule and get the
> result in 1 file.
> T.I.A
|||Just to add...the limit is 3200 characters.
-Sue
On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
<anonymous@.discussions.microsoft.com> wrote:

>Does anyone know what is the limitation on SQL Server job
>SQL statement is ?. I am trying to create a job that has a
>long SQL (Select) statement but it does not allow me to
>put the whole statement (It truncates). What are the
>alternatives (NOT DTS or QA)? These are more that 15
>separeate SQL statements I need to schedule and get the
>result in 1 file.
>T.I.A
|||Thanks to all.........
I will use SP.......
[vbcol=seagreen]
>--Original Message--
has a
>Put your T-SQL code in a stored procedure?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||Although, I put the statements into a SP, I don't get the
same output in Scheduled job output as I get out of the QA
(I like to get it as it is in QA output).
Thanks.
[vbcol=seagreen]
>--Original Message--
has a
>Put your T-SQL code in a stored procedure?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||But EM might be more restrictive then 3200 characters. I recall a case a long time ago when I tested
it, and conclusion was that if you need more than what EM allows, you need to add the jobsteps using
sp_add_jobstep.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:djeav0140graejhho9kee8u1qkd68olvgf@.4ax.com...
> Just to add...the limit is 3200 characters.
> -Sue
> On Mon, 24 Jan 2005 09:21:45 -0800, "Ken"
> <anonymous@.discussions.microsoft.com> wrote:
>
|||I have 1 Select statement that is 3750 characters which
does not go into any job steps.........

>--Original Message--
>But EM might be more restrictive then 3200 characters. I
recall a case a long time ago when I tested
>it, and conclusion was that if you need more than what EM
allows, you need to add the jobsteps using[vbcol=seagreen]
>sp_add_jobstep.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>http://www.sqlug.se/
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:djeav0140graejhho9kee8u1qkd68olvgf@.4ax.com.. .
job[vbcol=seagreen]
has a
>
>.
>
|||If you are > 3200 characters, you cannot have it directly in the jobstep regardless of whether you
are using EM or call sp_add_jobstep directly. Use any of the other suggested methods (put it in a
stored procedure, or use CmdExec jobstep which calls OSQL.EXE with an inputfile).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:062b01c502e5$e2bc1330$a601280a@.phx.gbl...[vbcol=seagreen]
>I have 1 Select statement that is 3750 characters which
> does not go into any job steps.........
>
> recall a case a long time ago when I tested
> allows, you need to add the jobsteps using
> job
> has a
sql

job security and permission required

Hi,
What permission is required to create and execute the job successfully?
Switch job ownership to A, but A can't execute job successfully. In the job
, there is DTS and stored procedure. What permission is required?
Thank you.
YulingSee:
269074 INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

JOB Scheduling

I create my first job schedule to remove some unused data at mid-night.
As I want to do some modification in that job schedule, I don't know how to
retrieve that Job ,
Please help. and thanksIn Enterprise Manager, go into Management->SQL Server Agent->Jobs.
Double-click on the job.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:uZvwhXzaGHA.4424@.TK2MSFTNGP02.phx.gbl...
I create my first job schedule to remove some unused data at mid-night.
As I want to do some modification in that job schedule, I don't know how to
retrieve that Job ,
Please help. and thanks

JOB Scheduling

I create my first job schedule to remove some unused data at mid-night.
As I want to do some modification in that job schedule, I don't know how to
retrieve that Job ,
Please help. and thanksIn Enterprise Manager, go into Management->SQL Server Agent->Jobs.
Double-click on the job.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:uZvwhXzaGHA.4424@.TK2MSFTNGP02.phx.gbl...
I create my first job schedule to remove some unused data at mid-night.
As I want to do some modification in that job schedule, I don't know how to
retrieve that Job ,
Please help. and thankssql

Job Schedules Not Schedu;ling

I can execute the following file to create jobs/ job
steps/ and related job schedules in SQL Analyzer ...
however the job is never scheduled. I can not identify
anything that is incorrect.
The commands process properly... and I can browse the
resulting msdb table entries in sys_jobs, sys_jobsteps,
and sys_jobschedules... however nothing ever gets
scheduled.
Please provide assistance where appropriate.
USE MSDB
EXEC sp_add_job
@.job_name='MailPointDBEmailFTCTPopulation',
@.enabled=1,
@.notify_level_eventlog=3
EXEC sp_add_jobstep
@.job_name='MailPointDBEmailFTCTPopulation',
@.step_name='EmailFTCTPopulation',
@.subsystem='TSQL',
@.command='EXEC sp_fulltext_table Email, ''update_index'''
EXEC sp_add_jobschedule
@.job_name='MailPointDBEmailFTCTPopulation',
@.name='MailPointDBEmailFTCTPopulation',
@.enabled=1,
@.freq_type=4,
@.freq_interval=1,
@.active_start_time=183000
EXEC sp_add_job
@.job_name='MailPointDBDocumentFTCTPopulation',
@.enabled=1,
@.notify_level_eventlog=3
EXEC sp_add_jobstep
@.job_name='MailPointDBDocumentFTCTPopulation',
@.step_name='DocumentFTCTPopulation',
@.subsystem='TSQL',
@.command='EXEC sp_fulltext_table
Document, ''update_index'''
EXEC sp_add_jobschedule
@.job_name='MailPointDBDocumentFTCTPopulation',
@.name='MailPointDBDocumentFTCTPopulation',
@.enabled=1,
@.freq_type=4,
@.freq_interval=1,
@.active_start_time=183000
GOis agent running on your server ?
jobi
"Philip" <plippard@.nc.rr.com> wrote in message
news:154f01c35247$39bb07a0$a001280a@.phx.gbl...
> I can execute the following file to create jobs/ job
> steps/ and related job schedules in SQL Analyzer ...
> however the job is never scheduled. I can not identify
> anything that is incorrect.
> The commands process properly... and I can browse the
> resulting msdb table entries in sys_jobs, sys_jobsteps,
> and sys_jobschedules... however nothing ever gets
> scheduled.
> Please provide assistance where appropriate.
> USE MSDB
> EXEC sp_add_job
> @.job_name='MailPointDBEmailFTCTPopulation',
> @.enabled=1,
> @.notify_level_eventlog=3
> EXEC sp_add_jobstep
> @.job_name='MailPointDBEmailFTCTPopulation',
> @.step_name='EmailFTCTPopulation',
> @.subsystem='TSQL',
> @.command='EXEC sp_fulltext_table Email, ''update_index'''
> EXEC sp_add_jobschedule
> @.job_name='MailPointDBEmailFTCTPopulation',
> @.name='MailPointDBEmailFTCTPopulation',
> @.enabled=1,
> @.freq_type=4,
> @.freq_interval=1,
> @.active_start_time=183000
> EXEC sp_add_job
> @.job_name='MailPointDBDocumentFTCTPopulation',
> @.enabled=1,
> @.notify_level_eventlog=3
> EXEC sp_add_jobstep
> @.job_name='MailPointDBDocumentFTCTPopulation',
> @.step_name='DocumentFTCTPopulation',
> @.subsystem='TSQL',
> @.command='EXEC sp_fulltext_table
> Document, ''update_index'''
> EXEC sp_add_jobschedule
> @.job_name='MailPointDBDocumentFTCTPopulation',
> @.name='MailPointDBDocumentFTCTPopulation',
> @.enabled=1,
> @.freq_type=4,
> @.freq_interval=1,
> @.active_start_time=183000
> GO
>

Job Question

HI,
I have multiple SQL servers and i am planning to create a job and deploy to
all the servers instead of deploying that job one by one in all servers and
generate report from one server instead of all (consolidation) later to see
on which server the job has failed. What best options do i have to link all
of them together? SO far i have known of linked server and making master and
target server. Anything else? or which one is better bewteen this two?
TIA
Rupart,
I would prefer using a master server and several target servers in this
scenario. The job status can be viewed locally on the target server or
remotely on the master server. Note, the job definition cannot be changed
on the target server. Also note that a target server (to my knowledge) can
only be associated with one master server at a time.
HTH
Jerry
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:F6C965C6-D4A8-4697-B482-7D37C0BCE9F7@.microsoft.com...
> HI,
> I have multiple SQL servers and i am planning to create a job and deploy
> to
> all the servers instead of deploying that job one by one in all servers
> and
> generate report from one server instead of all (consolidation) later to
> see
> on which server the job has failed. What best options do i have to link
> all
> of them together? SO far i have known of linked server and making master
> and
> target server. Anything else? or which one is better bewteen this two?
> TIA

Job Question

HI,
I have multiple SQL servers and i am planning to create a job and deploy to
all the servers instead of deploying that job one by one in all servers and
generate report from one server instead of all (consolidation) later to see
on which server the job has failed. What best options do i have to link all
of them together? SO far i have known of linked server and making master and
target server. Anything else? or which one is better bewteen this two?
TIARupart,
I would prefer using a master server and several target servers in this
scenario. The job status can be viewed locally on the target server or
remotely on the master server. Note, the job definition cannot be changed
on the target server. Also note that a target server (to my knowledge) can
only be associated with one master server at a time.
HTH
Jerry
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:F6C965C6-D4A8-4697-B482-7D37C0BCE9F7@.microsoft.com...
> HI,
> I have multiple SQL servers and i am planning to create a job and deploy
> to
> all the servers instead of deploying that job one by one in all servers
> and
> generate report from one server instead of all (consolidation) later to
> see
> on which server the job has failed. What best options do i have to link
> all
> of them together? SO far i have known of linked server and making master
> and
> target server. Anything else? or which one is better bewteen this two?
> TIA

Job Question

HI,
I have multiple SQL servers and i am planning to create a job and deploy to
all the servers instead of deploying that job one by one in all servers and
generate report from one server instead of all (consolidation) later to see
on which server the job has failed. What best options do i have to link all
of them together? SO far i have known of linked server and making master and
target server. Anything else? or which one is better bewteen this two?
TIARupart,
I would prefer using a master server and several target servers in this
scenario. The job status can be viewed locally on the target server or
remotely on the master server. Note, the job definition cannot be changed
on the target server. Also note that a target server (to my knowledge) can
only be associated with one master server at a time.
HTH
Jerry
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:F6C965C6-D4A8-4697-B482-7D37C0BCE9F7@.microsoft.com...
> HI,
> I have multiple SQL servers and i am planning to create a job and deploy
> to
> all the servers instead of deploying that job one by one in all servers
> and
> generate report from one server instead of all (consolidation) later to
> see
> on which server the job has failed. What best options do i have to link
> all
> of them together? SO far i have known of linked server and making master
> and
> target server. Anything else? or which one is better bewteen this two?
> TIAsql

Job owned by a non-sysadmin fails to run

Hi,
The preblem has been already discussed but none of answers help me.
I have a SQL Server 2000 SP4. Users that are not sysadmins create jobs for
SQL Server Agent. These jobs consist of a single CmdExec step.
As advised in many posts I created a Proxy SQL Server Agent account
(sqlproxy) but this did not help me, the jobs still fail to run. This
account is a windows account. I made this account belong to the sysadmins
role of SQL Server.
Both SQL Server and SQL Server Agent run under a special account
(sqlservice).
I added the account sqlservice to Administrators as advised in the article
http://support.microsoft.com/kb/833559 and even added to Administrators the
account sqlproxy, although the article states I did not have to.
The message I get in EventLog is like below:
-- message start
SQL Server Scheduled Job '<job name>' (0xEFC686299E5B9249957CC5FCF5C782C4) -
Status: Failed - Invoked on: 2006-12-18 12:06:06 - Message: The job failed.
The Job was invoked by User <domain>\<user>. The last step to run was step
1 (<step name> ).
-- message end
The command of the CmdExec step runs fine if I login as user as well as
sqlproxy.
I set the output file in advanced properties of the CmdExec step but did not
see in that file anything. Looks like the job does not start at all.
When I add user acocunt to the group Administrators the job runs
successfully, but this is definitely not an option.
I would appreciate any help as I run out of ideas already.Try changing the owner of the job to SA or another sysadmin.
Ivan Gerken wrote:
> Hi,
> The preblem has been already discussed but none of answers help me.
> I have a SQL Server 2000 SP4. Users that are not sysadmins create jobs for
> SQL Server Agent. These jobs consist of a single CmdExec step.
> As advised in many posts I created a Proxy SQL Server Agent account
> (sqlproxy) but this did not help me, the jobs still fail to run. This
> account is a windows account. I made this account belong to the sysadmins
> role of SQL Server.
> Both SQL Server and SQL Server Agent run under a special account
> (sqlservice).
> I added the account sqlservice to Administrators as advised in the article
> http://support.microsoft.com/kb/833559 and even added to Administrators th
e
> account sqlproxy, although the article states I did not have to.
> The message I get in EventLog is like below:
> -- message start
> SQL Server Scheduled Job '<job name>' (0xEFC686299E5B9249957CC5FCF5C782C4)
-
> Status: Failed - Invoked on: 2006-12-18 12:06:06 - Message: The job failed
.
> The Job was invoked by User <domain>\<user>. The last step to run was ste
p
> 1 (<step name> ).
> -- message end
> The command of the CmdExec step runs fine if I login as user as well as
> sqlproxy.
> I set the output file in advanced properties of the CmdExec step but did n
ot
> see in that file anything. Looks like the job does not start at all.
> When I add user acocunt to the group Administrators the job runs
> successfully, but this is definitely not an option.
> I would appreciate any help as I run out of ideas already.|||This quick solution is not an option.
Jobs are created from an external application (Business Desk of Commerce
Server 2002). A created job is owned by the user logged in to the
application (using win integrated authentication).
I definitely don't want to give users administrative privileges.
"PSPDBA" <DissendiumDBA@.gmail.com> wrote in message
news:1166704870.838450.230270@.f1g2000cwa.googlegroups.com...
> Try changing the owner of the job to SA or another sysadmin.
>|||For debugging, try temporarily changing the job owner to 'sa' as PSPDBA
suggested. If the job still fails, then the problem is related to running
as a job rather than a security issue.
Exactly what does the CmdExec step do? Are mapped drives accessed?
Hope this helps.
Dan Guzman
SQL Server MVP
"Ivan Gerken" <testivan@.waterproof.nl> wrote in message
news:uE$3GeRJHHA.420@.TK2MSFTNGP06.phx.gbl...
> This quick solution is not an option.
> Jobs are created from an external application (Business Desk of Commerce
> Server 2002). A created job is owned by the user logged in to the
> application (using win integrated authentication).
> I definitely don't want to give users administrative privileges.
> "PSPDBA" <DissendiumDBA@.gmail.com> wrote in message
> news:1166704870.838450.230270@.f1g2000cwa.googlegroups.com...
>|||Looks like I have a problem with CmdExec jobs in general.
I changed the step command to "dir c:\temp" and it ran fine when owned by an
admin but failed when owned by a user. In case of being owned by a user even
the output file was not created. The folder c:\temp has "full control"
permission granted to everyone.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:42FF0C9C-4AFC-42AF-9464-0931A1DDE13B@.microsoft.com...
> I'm starting to run out of ideas. Do you have any CmdExec job steps that
> successfully run as non-sysadmin users or is it just dmlrun.exe that has
> the problem?
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP|||Lets make sure I have the relevant details right since so much has been
discussed in this thread:
- SQL Server service and SQL Server Agent service run under the same
account
- The account is a member of the local administrators group
- xp_cmdshell runs fine when involed by non-sysadmins
- CmdExec jobs fail for jobs owned by non-sysadmins
What I find strange is that xp_cmdshell works but CmdExec doesn't. I can
see how this might be the case if you used different service accounts and
the SQL Agent service account lacked the advanced user rights (e.g. 'act as
part of the operating system' and 'replace a process-level token') that are
needed to switch security context to the proxy account.
Can you double-check to ensure the same service account is used for SQL
Server and SQL Server Agent services? If you have made changes to service
account security, have you since restarted the service? In some cases, a
server restart in needed in order for security changes to fully take affect.
Happy Holidays
Dan Guzman
SQL Server MVP
"Ivan Gerken" <testivan@.waterproof.nl> wrote in message
news:%239rDNPAKHHA.2236@.TK2MSFTNGP02.phx.gbl...
> Looks like I have a problem with CmdExec jobs in general.
> I changed the step command to "dir c:\temp" and it ran fine when owned by
> an admin but failed when owned by a user. In case of being owned by a user
> even the output file was not created. The folder c:\temp has "full
> control" permission granted to everyone.
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:42FF0C9C-4AFC-42AF-9464-0931A1DDE13B@.microsoft.com...
>|||- SQL Server service and SQL Server Agent service run under the same
account
Yes, referred to earlier as sqlservice. However, the services MSSEARCH,
MSSQLServerADHelper, MSSQLServerOLAPService run under Local System (I think
it hardly matters but just in case).
- The account is a member of the local administrators group
Yes, plus OLAP Administrators and Users.
- xp_cmdshell runs fine when involed by non-sysadmins
Yes. User account is a member of Users and Remote Desktop Users.
- CmdExec jobs fail for jobs owned by non-sysadmins
Yes, even after restarting both MSSQLSERVER and SQLSERVERAGENT.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:A7AC10BD-AE8F-4C96-ADE3-1F1603A38D9C@.microsoft.com...
> Lets make sure I have the relevant details right since so much has been
> discussed in this thread:
> - SQL Server service and SQL Server Agent service run under the same
> account
> - The account is a member of the local administrators group
> - xp_cmdshell runs fine when involed by non-sysadmins
> - CmdExec jobs fail for jobs owned by non-sysadmins
> What I find strange is that xp_cmdshell works but CmdExec doesn't. I can
> see how this might be the case if you used different service accounts and
> the SQL Agent service account lacked the advanced user rights (e.g. 'act
> as part of the operating system' and 'replace a process-level token') that
> are needed to switch security context to the proxy account.
> Can you double-check to ensure the same service account is used for SQL
> Server and SQL Server Agent services? If you have made changes to service
> account security, have you since restarted the service? In some cases, a
> server restart in needed in order for security changes to fully take
> affect.
> --
> Happy Holidays
> Dan Guzman
> SQL Server MVP|||> Yes, even after restarting both MSSQLSERVER and SQLSERVERAGENT.
Have you restarted the server since you added the sqlservice account to the
local Administrator's group? Although not normally required, I've seen
occasions where a restart was needed to pickup the group membership change.
BTW, are there any related messages in the SQL Agent log files?
Hope this helps.
Dan Guzman
SQL Server MVP
"Ivan Gerken" <testivan@.waterproof.nl> wrote in message
news:uVs$ZSQKHHA.2232@.TK2MSFTNGP02.phx.gbl...
>- SQL Server service and SQL Server Agent service run under the same
>account
> Yes, referred to earlier as sqlservice. However, the services MSSEARCH,
> MSSQLServerADHelper, MSSQLServerOLAPService run under Local System (I
> think it hardly matters but just in case).
> - The account is a member of the local administrators group
> Yes, plus OLAP Administrators and Users.
> - xp_cmdshell runs fine when involed by non-sysadmins
> Yes. User account is a member of Users and Remote Desktop Users.
> - CmdExec jobs fail for jobs owned by non-sysadmins
> Yes, even after restarting both MSSQLSERVER and SQLSERVERAGENT.
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:A7AC10BD-AE8F-4C96-ADE3-1F1603A38D9C@.microsoft.com...
>|||Dan,
Many thanks for a great hint! I checked SQL Agent log and found there the
following message:
[136] Job <job name> reported: Warning: cannot write logfile
c:\temp\dmout.txt. Error 5 : Access is denied
Then, after I have cleared the "Output file" box the job executed
successfully. So the problem seems to be solved.
However, I find this error very odd because full control is granted to
everyone on c:\temp
Many thanks for your help!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:C7F5CB7B-970A-4EFF-885C-772ED21ECF0A@.microsoft.com...
> Have you restarted the server since you added the sqlservice account to
> the local Administrator's group? Although not normally required, I've
> seen occasions where a restart was needed to pickup the group membership
> change.
> BTW, are there any related messages in the SQL Agent log files?
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Ivan Gerken" <testivan@.waterproof.nl> wrote in message
> news:uVs$ZSQKHHA.2232@.TK2MSFTNGP02.phx.gbl...
>|||I'm glad you were able to get it sorted out. I'm sorry I didn't suggest
checking the log earlier.

> However, I find this error very odd because full control is granted to
> everyone on c:\temp
The error 5 can be caused by the file being used by another process or that
the read-only attribute is set.
Hope this helps.
Dan Guzman
SQL Server MVP
"Ivan Gerken" <testivan@.waterproof.nl> wrote in message
news:eLhoAacKHHA.3424@.TK2MSFTNGP02.phx.gbl...
> Dan,
> Many thanks for a great hint! I checked SQL Agent log and found there the
> following message:
> [136] Job <job name> reported: Warning: cannot write logfile
> c:\temp\dmout.txt. Error 5 : Access is denied
> Then, after I have cleared the "Output file" box the job executed
> successfully. So the problem seems to be solved.
> However, I find this error very odd because full control is granted to
> everyone on c:\temp
> Many thanks for your help!
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:C7F5CB7B-970A-4EFF-885C-772ED21ECF0A@.microsoft.com...
>

Job not working

The output message is :
" DTSRun: Cannot create COM Server to load and execute
DTS Package. Error -2147221164 (80040154): Class not
registered "Was the package created on a different version of SQL Server ?
have you registered the DTS dlls?
If you have then you may want to reregister them.
Redistributing DTS with your program
http://www.sqldts.com/default.aspx?6,105,225,0,1
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:084a01c3b8bc$74b5a690$a501280a@.phx.gbl...
> The output message is :
> " DTSRun: Cannot create COM Server to load and execute
> DTS Package. Error -2147221164 (80040154): Class not
> registered "
>

Job History report

Hello all,

I need to create a report on a certain Job on my server. It should look exactly like the "View History" window.

to do that, i need to find a way to group the logged steps by the job executions. The problem is that in the sysjobhistory table there's only a instance_id field that runs incrementally, with no way to identify the execution…

any ideas?

You'll need to join so sysjobs and sysoperators if you want the Job Name and Operators that were emailed, net sent or paged.

You might be able to group the run_date and run_time together and use this for your "key" to group the job steps together. Note: run_time is in a 24 hour format and is not left zero filled (i.e. 10001 is 1:00:01 am, 152531 is 15:25:31 pm).

convert(varchar(8), run_date) + right('000000' + convert(varchar(6), run_time), 6) -->> will give you the date and hhmmss the step executed (i.e. 20061225010001).

You could parse the results (maybe using hours and/or minutes) to group the steps together.

The above is a quick and dirty and depending upon how often and how long your jobs run, may not work.

Since the format of job history is consitent with step_id of 0 as the job completion step, you can write a stored procedure and use a cursor to group the steps (read all the steps and "break" each time a step_id of 0 is encountered).

|||

Thanks,

The first way you wrote will not work since you cannot group on Running Date & Time - this group will not identify all the steps in a certain run in the same group.

I also thought of the second way, but it seemed too costly.

How does the "view job history" window know how to separate the job executions?

|||

Liran, that is why I wrote that the first step "may not work". If your job ran once each hour, started at 1 minute past the hour and ran for less than 59 minutes every time, the first method would work since each step would have the same date and hour time stamp. Obviously this won't work if your job starts at 59 minutes after the hour and runs for more than one minute or runs for more than one hour.

Not sure how the "view job history" works but would imagine it does a similar activity as what I described for writing a stored procedure. Since you can't have the same job name executing at the same time on the same server, the starting date/time of the job and each of it's steps will be in chronological order; doesn't matter if the job runs more than one our or spans over multiple days.

Another option might be to add the duration (from step_id = 0) to the start date/time to get the ending date/time of the job (NOT the steps). You could then choose any of the rows in sysjobhistory that fall between the start date/time and the calculated ending date/time of the job.

You said you had an idea, why don't you describe it and we might be able to expand upon it...

|||

OK, Now I understood what you meant, but this method is not relevant to me since this job runs for more then 1 hour with 1 min between each run…

About the second Idea, I meant I also thought of the second idea you wrote (with the procedure and cursor) but it seems to me too costly to be executed every time the report is viewed…

Thanks, I just thought there's somewhere a "job running instance id" that I'm overlooking…

|||

Pls chek the following post..It may help you

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1033004&SiteID=1

Job failure notifications for non-administrative users

Some of my power users create their own SQL Agent jobs. All well and
good. However, I don't wish to give them System Administrator
privileges, and when they create their jobs, the check box to "e-mail
operator" in the job notifications tab is greyed out. Is this a
feature? I'm having difficulty finding documentation on it, or even any
mention, where a distinction is made between administrators and
standard users.
Other than setting up the notifications myself after the jobs are
created, is there any way around this issue? This is on SQL 2000 EE,
service pack 3a, running on Windows 2K Advanced Server.
Thanks,
Steve
Hi Steve,
A distinction is made between administrators and standard users?
This depends of as configured the Services SQL Server Agent, the account is
"Local System" or is a administrator account o User Email Account?.
If is "Local System", this can you problem.
Hermilson Tinoco
"Steve" wrote:

> Some of my power users create their own SQL Agent jobs. All well and
> good. However, I don't wish to give them System Administrator
> privileges, and when they create their jobs, the check box to "e-mail
> operator" in the job notifications tab is greyed out. Is this a
> feature? I'm having difficulty finding documentation on it, or even any
> mention, where a distinction is made between administrators and
> standard users.
> Other than setting up the notifications myself after the jobs are
> created, is there any way around this issue? This is on SQL 2000 EE,
> service pack 3a, running on Windows 2K Advanced Server.
> Thanks,
> Steve
>
|||SQL Server Agent is running under the same account as the SQL Server, a
domain account set up to be a local administrator.
Note that as an administrator I can add notifications to both my own
jobs and my users' jobs; it's just the users that can't add
notifications to their own jobs.
Steve

Job failure notifications for non-administrative users

Some of my power users create their own SQL Agent jobs. All well and
good. However, I don't wish to give them System Administrator
privileges, and when they create their jobs, the check box to "e-mail
operator" in the job notifications tab is greyed out. Is this a
feature? I'm having difficulty finding documentation on it, or even any
mention, where a distinction is made between administrators and
standard users.
Other than setting up the notifications myself after the jobs are
created, is there any way around this issue? This is on SQL 2000 EE,
service pack 3a, running on Windows 2K Advanced Server.
Thanks,
SteveHi Steve,
A distinction is made between administrators and standard users'
This depends of as configured the Services SQL Server Agent, the account is
"Local System" or is a administrator account o User Email Account?.
If is "Local System", this can you problem.
Hermilson Tinoco
"Steve" wrote:
> Some of my power users create their own SQL Agent jobs. All well and
> good. However, I don't wish to give them System Administrator
> privileges, and when they create their jobs, the check box to "e-mail
> operator" in the job notifications tab is greyed out. Is this a
> feature? I'm having difficulty finding documentation on it, or even any
> mention, where a distinction is made between administrators and
> standard users.
> Other than setting up the notifications myself after the jobs are
> created, is there any way around this issue? This is on SQL 2000 EE,
> service pack 3a, running on Windows 2K Advanced Server.
> Thanks,
> Steve
>|||SQL Server Agent is running under the same account as the SQL Server, a
domain account set up to be a local administrator.
Note that as an administrator I can add notifications to both my own
jobs and my users' jobs; it's just the users that can't add
notifications to their own jobs.
Steve

job failed after domain IP address changed

I've create a maintenance plan using the SQLserver Wizard.

The jobs work correctly until we change the IP address of the server with the following trace :

The job failed. Unable to determine if the owner (DOMAIN\Login) of job Transaction Log Backup Job for DB Maintenance Plan 'BASE' has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\login'. [SQLSTATE 42000] (Error 8198)).

Can somebpody explain me what occured ?Howdy

I have seen this a lot on SQL 7 and it seems the NT authentication/ SQL interface neve rreally worked properly.

Easiest way ( and usually the best way of going anyway ) is get sa to own all jobs, then unless its a very secure server, all will run fine and if you change the IP adderess of the server, as sa is local, it wont make any difference.

Cheers

SG.