Shuxclams
Diamond Member
- Oct 10, 1999
- 9,286
- 15
- 81
Shuxclams
Diamond Member
- Oct 10, 1999
- 9,286
- 15
- 81
sp_add_job [@job_name =] '<job name>'
[,[@enabled =] <0 for no, 1 for yes>]
[,[@description =] '<description of the job>']
[,[@start_step_id =] <ID of the step you want to start at>]
[,[@category_name =] '<category>']
[,[@category_id =] <category ID>]
[,[@owner_login_name =] '<login>']
[,[@notify_level_eventlog =] <eventlog level>]
[,[@notify_level_email =] <email level>]
[,[@notify_level_netsend =] <netsend level>]
[,[@notify_level_page =] <page level>]
[,[@notify_email_operator_name =]
'<name of operator to email>']
[,[@notify_netsend_operator_name =]
'<name of operator for network message>']
[,[@notify_page_operator_name =] '<name of operator to page>']
[,[@delete_level =] <delete level>]
[,[@job_id =] <job id> OUTPUT]
Again, most of the parameters here are self-describing, but let's touch on some of the more sticky ones.
<< @start_step_id: This one is going to default to 1, and that's almost always going to be the place to leave it. We'll be adding steps
shortly, but those steps will have identifiers to them, and this just let's the SQL Server Agent know where to begin the job.
@category_name: This one equates directly with the category we saw in the EM. It will often be none, but could be a Database
Maintenance (another common choice), Full Text, Web Assistant or Replication category.
@category_id: This is just a way of providing a category without being dependent on a particular language.
@notify_level_eventlog: For each type of notification, this determines under what condition the notification occurs. In EM, this was the
far right combo box in the notification tab. To use this sproc though, we need to supply some constant values to indicate when we want
the notification to happen. The constants are: >>
[/b]JOY!
SHUX
[,[@enabled =] <0 for no, 1 for yes>]
[,[@description =] '<description of the job>']
[,[@start_step_id =] <ID of the step you want to start at>]
[,[@category_name =] '<category>']
[,[@category_id =] <category ID>]
[,[@owner_login_name =] '<login>']
[,[@notify_level_eventlog =] <eventlog level>]
[,[@notify_level_email =] <email level>]
[,[@notify_level_netsend =] <netsend level>]
[,[@notify_level_page =] <page level>]
[,[@notify_email_operator_name =]
'<name of operator to email>']
[,[@notify_netsend_operator_name =]
'<name of operator for network message>']
[,[@notify_page_operator_name =] '<name of operator to page>']
[,[@delete_level =] <delete level>]
[,[@job_id =] <job id> OUTPUT]
Again, most of the parameters here are self-describing, but let's touch on some of the more sticky ones.
<< @start_step_id: This one is going to default to 1, and that's almost always going to be the place to leave it. We'll be adding steps
shortly, but those steps will have identifiers to them, and this just let's the SQL Server Agent know where to begin the job.
@category_name: This one equates directly with the category we saw in the EM. It will often be none, but could be a Database
Maintenance (another common choice), Full Text, Web Assistant or Replication category.
@category_id: This is just a way of providing a category without being dependent on a particular language.
@notify_level_eventlog: For each type of notification, this determines under what condition the notification occurs. In EM, this was the
far right combo box in the notification tab. To use this sproc though, we need to supply some constant values to indicate when we want
the notification to happen. The constants are: >>
[/b]JOY!
SHUX
private parts
dim is some good donuts
if'n
youz cliks dis
den
dis happ'ns
else
nuffin happ'ns
end sub
dim is some good donuts
if'n
youz cliks dis
den
dis happ'ns
else
nuffin happ'ns
end sub
same here IBhackNU
anyways, ive got 2 800p C++ books to back u up
if (!*Shux->brain)
{
throwBook(&b_cpp, 2);
laughAt(Coords(Shux), 10);
}
how ya like them apples?
anyways, ive got 2 800p C++ books to back u up
if (!*Shux->brain)
{
throwBook(&b_cpp, 2);
laughAt(Coords(Shux), 10);
}
how ya like them apples?
wazzup!!!! or in the words of the imortal buddwieser frogs
bigfrog: WAH
fly: ZZZ
lizard: UUPPP
nuthin here im alive at work
bigfrog: WAH
fly: ZZZ
lizard: UUPPP
nuthin here im alive at work
oh dude's your books only got 1400 pages??? well lemme find a mcse tutorial suite and show you whose who. 10 inches of premium microsoft assininity, or take em out of the cardboard casing and you got a good bombing run ready to go
OK, now I'm just going to go down to the book store and find one of those developer suites packages to load up on some ammo!
Hey, I have a question.. I have to cook a Turkey for the Family thing this year... I've never cooked one before.. How long and at what temp will it take to cook a 23 pound turkey?
I was told to cook it at 200 deg.. until the thingy pops up, but how long is it going to take? 12-18 hours? I'd hate for THursday noon come around and the turkey still has another 4 hours to cook! :|
I was told to cook it at 200 deg.. until the thingy pops up, but how long is it going to take? 12-18 hours? I'd hate for THursday noon come around and the turkey still has another 4 hours to cook! :|
Adul
Elite Member
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 24K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter