Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeraldaUse another job step.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeralda

Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeraldaUse another job step.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeraldasql

Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeralda
Use another job step.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeralda

Job Step command altering

Is their a way to alter a job step command using T-SQL rather than using
the GUI in enterprise manager?
For example, if I have an existing command of:
BACKUP DATABASE [CE90] TO Disk = 'CE90_20050118.bak' WITH NOINIT ,
NOUNLOAD , NAME = N'CE90 Full Backup', NOSKIP , STATS = 10, NOFORMAT
Is it possible to alter the above command to a different disk device using
T-SQL?
Message posted via http://www.sqlmonster.com
You an use sp_update_jobstep. You can find more information
on this stored procedure in books online.
-Sue
On Wed, 02 Feb 2005 19:25:39 GMT, "Robert Richards via
SQLMonster.com" <forum@.SQLMonster.com> wrote:

>Is their a way to alter a job step command using T-SQL rather than using
>the GUI in enterprise manager?
>For example, if I have an existing command of:
>BACKUP DATABASE [CE90] TO Disk = 'CE90_20050118.bak' WITH NOINIT ,
>NOUNLOAD , NAME = N'CE90 Full Backup', NOSKIP , STATS = 10, NOFORMAT
>Is it possible to alter the above command to a different disk device using
>T-SQL?

Job Step command altering

Is their a way to alter a job step command using T-SQL rather than using
the GUI in enterprise manager?
For example, if I have an existing command of:
BACKUP DATABASE [CE90] TO Disk = 'CE90_20050118.bak' WITH NOINIT ,
NOUNLOAD , NAME = N'CE90 Full Backup', NOSKIP , STATS = 10, NOFORMAT
Is it possible to alter the above command to a different disk device using
T-SQL?
Message posted via http://www.droptable.comYou an use sp_update_jobstep. You can find more information
on this stored procedure in books online.
-Sue
On Wed, 02 Feb 2005 19:25:39 GMT, "Robert Richards via
droptable.com" <forum@.droptable.com> wrote:

>Is their a way to alter a job step command using T-SQL rather than using
>the GUI in enterprise manager?
>For example, if I have an existing command of:
>BACKUP DATABASE [CE90] TO Disk = 'CE90_20050118.bak' WITH NOINIT ,
>NOUNLOAD , NAME = N'CE90 Full Backup', NOSKIP , STATS = 10, NOFORMAT
>Is it possible to alter the above command to a different disk device using
>T-SQL?

Job Step command altering

Is their a way to alter a job step command using T-SQL rather than using
the GUI in enterprise manager?
For example, if I have an existing command of:
BACKUP DATABASE [CE90] TO Disk = 'CE90_20050118.bak' WITH NOINIT ,
NOUNLOAD , NAME = N'CE90 Full Backup', NOSKIP , STATS = 10, NOFORMAT
Is it possible to alter the above command to a different disk device using
T-SQL?
--
Message posted via http://www.sqlmonster.comYou an use sp_update_jobstep. You can find more information
on this stored procedure in books online.
-Sue
On Wed, 02 Feb 2005 19:25:39 GMT, "Robert Richards via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>Is their a way to alter a job step command using T-SQL rather than using
>the GUI in enterprise manager?
>For example, if I have an existing command of:
>BACKUP DATABASE [CE90] TO Disk = 'CE90_20050118.bak' WITH NOINIT ,
>NOUNLOAD , NAME = N'CE90 Full Backup', NOSKIP , STATS = 10, NOFORMAT
>Is it possible to alter the above command to a different disk device using
>T-SQL?

Job step cmdexec for applicaiton

Hi,
In a job, as one of the last steps, I want to execute an application.

Can someone please let me know the command (cmdexec) to be put

Right now, I have put "E:\Program Files\Postscript\gsview\gsview32.exe" which is not working

I know for dts packages, the command is
dtsrun /FE:\temp\Let-Stat MIS\Letters_Import.dts /NLetters_Import

Thanks and regards
AbhiUse the xp_cmdshell procedure to execute commands from a system prompt.

blindmansql

Job Step

I have a job step that needs to run with a different parameter on Sunday.
The job step is of type Operating System Command. This step kicks of an
executable.
Can you help me with a solution?
Thanks,
ChrisHow about creating a second step that has different parameters. Then create
a second job that runs prior to this job. In this second job, you can check
to see if it is Sunday and then enable appropriate step on first job and
disable the other one (and vice versa).
"csl" <kcl1998@.hotmail.com> wrote in message
news:uCOv4089HHA.3548@.TK2MSFTNGP06.phx.gbl...
>I have a job step that needs to run with a different parameter on Sunday.
> The job step is of type Operating System Command. This step kicks of an
> executable.
> Can you help me with a solution?
> Thanks,
> Chris
>|||Hi,
I do this with three job steps. Job step 2 has the 6 days a week command,
and job step 3 has the sunday command. In job step one I put a statement
that calls RAISERROR('whatever', 16, 1) on Sunday. Then I set up step one to
go to step 2 on success and step 3 on failure. Both steps 2 and 3 quit
reporting success on success and quit reporting failure on failure.
Or, just create two SQL Agent jobs. One runs weekly on Mon-Sat, and the
other runs weekly on Sun.
--
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
"Dragon" <noSpam_Badill@.hotmail.com> wrote in message
news:uk2aK689HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
> How about creating a second step that has different parameters. Then
> create a second job that runs prior to this job. In this second job, you
> can check to see if it is Sunday and then enable appropriate step on first
> job and disable the other one (and vice versa).
> "csl" <kcl1998@.hotmail.com> wrote in message
> news:uCOv4089HHA.3548@.TK2MSFTNGP06.phx.gbl...
>>I have a job step that needs to run with a different parameter on Sunday.
>> The job step is of type Operating System Command. This step kicks of an
>> executable.
>> Can you help me with a solution?
>> Thanks,
>> Chris
>>
>

Job problem

Hello,
I have a job where in one of the steps I'm coping a
database backup file from one server to the other using
an operating system command xcopy. The command I'm using
is below, but the job keeps failing on this step. The
error I get is "The job failed. The Job was invoked by
User TST-SQL\VDURAN. The last step to run was step 3
(copyfile).".
The command works fine if I execute from the actual
command prompt of the source server. My destination
server directory is shared and I have set my permssions
to full control for everyone. Please help.
xcopy d:\backups\TestBackup\OrdersDB.bak
\\duran\DBBackups\
TIA,
VicWhat is the exact error for step 3 ? Is this using a CmdExec job step ?
If you look at the step history you should see the exit code for the step
and the error.
If the file exists you will want to use the /Y switch for xcopy to allow
overwring of the file although this would generally hang the step if this
was the issue. How about just using copy /Y does this work ?
I take it that the SQLService account is running under a domain account ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Vic" <vduran@.specpro-inc.com> wrote in message
news:009c01c3d535$d23fb7c0$a101280a@.phx.gbl...
> Hello,
> I have a job where in one of the steps I'm coping a
> database backup file from one server to the other using
> an operating system command xcopy. The command I'm using
> is below, but the job keeps failing on this step. The
> error I get is "The job failed. The Job was invoked by
> User TST-SQL\VDURAN. The last step to run was step 3
> (copyfile).".
> The command works fine if I execute from the actual
> command prompt of the source server. My destination
> server directory is shared and I have set my permssions
> to full control for everyone. Please help.
> xcopy d:\backups\TestBackup\OrdersDB.bak
> \\duran\DBBackups\
>
> TIA,
> Vic|||Is it possible that you need to supply the actual path of
the xcopy command? Also, you may want to create the job
step to execute a command (.cmd) file rather than the
command itself. This would allow you to do some type of
eror code processing. It's been a long time since I've
done that in DOS batch files, but it should be doable.
Most likely you either have a path problem or a
permissions problem though.
I know this is a rather vague response, but hopefully it
will lead to something.
Matthew Bando
BandoM@.CSCTGI(remove).com
>--Original Message--
>Hello,
> I have a job where in one of the steps I'm coping a
>database backup file from one server to the other using
>an operating system command xcopy. The command I'm
using
>is below, but the job keeps failing on this step. The
>error I get is "The job failed. The Job was invoked by
>User TST-SQL\VDURAN. The last step to run was step 3
>(copyfile).".
> The command works fine if I execute from the actual
>command prompt of the source server. My destination
>server directory is shared and I have set my permssions
>to full control for everyone. Please help.
>xcopy d:\backups\TestBackup\OrdersDB.bak
>\\duran\DBBackups\
>
>TIA,
>Vic
>.
>|||Hello there.
I got kind of a similar issue with few jobs. To pin point
to the culprit, I set the DTS package to log the whole
process.
I found out which steps in my DTS package were failing and
not the generic SQL message from the job history, which
never says exactly what happened.
I have quite a few stpes in each job that uses windows
tasks. Two of those needs some time to be completed.
The first one, unzips a daily file to be run by other
steps to copy or update some tables.
The second step, copies the unzipped files to a different
server.
I applied two solutions for those command steps.
1. For the unzip command, I added an activeX step, which
loops while the file is being used by the DTS. Problem
solved here.
2. For the copy unzipped files to a different server (I
had to copy instead of moving files due to some internal
applications), I did take the step off the DTS and
schedule it to run a few minutes after the main job is
completed. Problem solved! for good.
Set the DTS log first to see exactly where your DTS is
failing, I bet is the move step (same thing happened to
me) I hope this helps. Good luck
>--Original Message--
>Hello,
> I have a job where in one of the steps I'm coping a
>database backup file from one server to the other using
>an operating system command xcopy. The command I'm using
>is below, but the job keeps failing on this step. The
>error I get is "The job failed. The Job was invoked by
>User TST-SQL\VDURAN. The last step to run was step 3
>(copyfile).".
> The command works fine if I execute from the actual
>command prompt of the source server. My destination
>server directory is shared and I have set my permssions
>to full control for everyone. Please help.
>xcopy d:\backups\TestBackup\OrdersDB.bak
>\\duran\DBBackups\
>
>TIA,
>Vic
>.
>

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.
How many times are you going to post this question?
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <MarkHYPERe@.discussions.microsoft.com> wrote in message
news:A6CBF4C4-0889-4526-91EA-BB325D99D859@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.
Ideally, it should take around the same amount of time. But are there any
logs in the sqlagent.out that might point to some errors or weird behaviour?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.
Ownership issues? Why did you leave the table owner name blank (you should
always specify dbo if there is only one such table)? If you are dbo you are
going to see different plan, perhaps, than SQL Server agent (remember that
SQL Server Agent jobs do not execute in the same context as you are
currently logged in to Query Analyzer).
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.
|||Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
see if it applies:
http://support.microsoft.com/default...30&Product=sql
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.
|||Thanks - that worked. Cheers to you. Sorry about the multiple posts. I was getting error messages when posting.
"Dan Guzman" wrote:

> Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
> see if it applies:
> http://support.microsoft.com/default...30&Product=sql
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
> news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> analyzer. If I run it from a job it takes 17.5061 minutes.
> dog. Are jobs governed. No other variables to consider - on a standalone
> network using the same box. The proc performs a series of updates, deletes,
> and inserts.
>
>
|||> Thanks - that worked. Cheers to you. Sorry about the multiple posts. I
was getting error messages when posting.
http://www.aspfaq.com/5007
sql

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.Ownership issues? Why did you leave the table owner name blank (you should
always specify dbo if there is only one such table)? If you are dbo you are
going to see different plan, perhaps, than SQL Server agent (remember that
SQL Server Agent jobs do not execute in the same context as you are
currently logged in to Query Analyzer).
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
see if it applies:
http://support.microsoft.com/default.aspx?scid=kb;en-us;249730&Product=sql
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||> Thanks - that worked. Cheers to you. Sorry about the multiple posts. I
was getting error messages when posting.
http://www.aspfaq.com/5007

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer. If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog. Are jobs governed. No other variables to consider - on a standalone network using the same box. The proc performs a series of updates, deletes, and inserts.
Thank you for your help.Ideally, it should take around the same amount of time. But are there any
logs in the sqlagent.out that might point to some errors or weird behaviour?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer.
If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog.
Are jobs governed. No other variables to consider - on a standalone networ
k using the same box. The proc performs a series of updates, deletes, and i
nserts.
Thank you for your help.Ownership issues? Why did you leave the table owner name blank (you should
always specify dbo if there is only one such table)? If you are dbo you are
going to see different plan, perhaps, than SQL Server agent (remember that
SQL Server Agent jobs do not execute in the same context as you are
currently logged in to Query Analyzer).
http://www.aspfaq.com/
(Reverse address to reply.)
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 to
see if it applies:
http://support.microsoft.com/defaul...730&Product=sql
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> I have a proc that takes 43 seconds to run if I run it from query
analyzer. If I run it from a job it takes 17.5061 minutes.
> The job command is EXEC [HYPERe]..[B33HiveMigration].
> I cut and paste it into Query Analyzer and whosh. From the job it's a
dog. Are jobs governed. No other variables to consider - on a standalone
network using the same box. The proc performs a series of updates, deletes,
and inserts.
> Thank you for your help.|||Thanks - that worked. Cheers to you. Sorry about the multiple posts. I wa
s getting error messages when posting.
"Dan Guzman" wrote:

> Make sure you have SET NOCOUNT ON in your proc and check out MSKB 249730 t
o
> see if it applies:
> http://support.microsoft.com/defaul...730&Product=sql
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Mark - HYPERe" <Mark - HYPERe@.discussions.microsoft.com> wrote in message
> news:DC69C3BE-3F01-4C92-B164-ADF680FB5220@.microsoft.com...
> analyzer. If I run it from a job it takes 17.5061 minutes.
> dog. Are jobs governed. No other variables to consider - on a standalone
> network using the same box. The proc performs a series of updates, delete
s,
> and inserts.
>
>|||> Thanks - that worked. Cheers to you. Sorry about the multiple posts. I
was getting error messages when posting.
http://www.aspfaq.com/5007

Job Performance Vs Running from Query Analyzer

I have a proc that takes 43 seconds to run if I run it from query analyzer.
If I run it from a job it takes 17.5061 minutes.
The job command is EXEC [HYPERe]..[B33HiveMigration].
I cut and paste it into Query Analyzer and whosh. From the job it's a dog.
Are jobs governed. No other variables to consider - on a standalone networ
k using the same box. The proc performs a series of updates, deletes, and i
nserts.
Thank you for your help.Ideally, it should take around the same amount of time. But are there any
logs in the sqlagent.out that might point to some errors or weird behaviour?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Job notification

Morning all!

My SQL server email job notifications have stopped working, but mails sent through the xp_sendmail command still work.

The only thing that has changed recently is the SQL server agent account passwords have been changed, these accounts are normal win2000 domain accounts.

Any ideas cos I am fully stumped?Have you tried testing the SQLMail Profile?

Support Services/SQLMail.

Are SQLMail and SQLAgentMail using the same mail profile?|||Already tested the SQL mail profile and that works ok,

How do I check which profile the sqlagentmail is using?|||Originally posted by SQLSlammer
Already tested the SQL mail profile and that works ok,

How do I check which profile the sqlagentmail is using?

Right click on SQL Agent/Properties and check that it is using the same mail profile.

Job Notification

On our SQL 2000 server there is no MAPI client or Outlook installed. The NET SEND command has been disabled on the server/network. The xp_sendmail can not be used due to SQL Mail not started due to no Outlook profile. I don't find that the Notification pa
ge allows to attach a command or batch file to do this job. It is just writing the Log to Application Event Log. Any feedback would be appreciated.
There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.
|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>
|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thanks...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>
|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz[vbcol=seagreen]
> "Richard Ding" wrote:
sql

Job Notification

On our SQL 2000 server there is no MAPI client or Outlook installed. The NET
SEND command has been disabled on the server/network. The xp_sendmail can n
ot be used due to SQL Mail not started due to no Outlook profile. I don't fi
nd that the Notification pa
ge allows to attach a command or batch file to do this job. It is just writi
ng the Log to Application Event Log. Any feedback would be appreciated.There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdo
sysmail in the Master database but could find them. Could you please let me
know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me
know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thank
s...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmai
l in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks.
.Fraz[vbcol=seagreen]
> "Richard Ding" wrote:
>

Job Notification

On our SQL 2000 server there is no MAPI client or Outlook installed. The NET SEND command has been disabled on the server/network. The xp_sendmail can not be used due to SQL Mail not started due to no Outlook profile. I don't find that the Notification page allows to attach a command or batch file to do this job. It is just writing the Log to Application Event Log. Any feedback would be appreciated.Check out SMTPMail on SQLDev.NET. You can either add that
as a job step on failure, or create a job that is called
when an alert executes. I believe there is an example of
the latter on that website.
FYI, SQL 2005 is going to support both MAPI-based and SMTP-
based email notification.
>--Original Message--
>On our SQL 2000 server there is no MAPI client or Outlook
installed. The NET SEND command has been disabled on the
server/network. The xp_sendmail can not be used due to SQL
Mail not started due to no Outlook profile. I don't find
that the Notification page allows to attach a command or
batch file to do this job. It is just writing the Log to
Application Event Log. Any feedback would be appreciated.
>.
>|||There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
> "Richard Ding" wrote:
> > There're about three ways to email a notification for a job:
> > 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> > 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> > 3. Install sp_send_cdosysmail and use this stored procedure to send out
> > email.
> >
> > I personally prefer sqlmail due to it's rich features. But be aware of its
> > total dependency on MS Exchange.
> >
> >
> > "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> > news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> > NET SEND command has been disabled on the server/network. The xp_sendmail
> > can not be used due to SQL Mail not started due to no Outlook profile. I
> > don't find that the Notification page allows to attach a command or batch
> > file to do this job. It is just writing the Log to Application Event Log.
> > Any feedback would be appreciated.
> >
> >
> >