Jobs

I have created several jobs which contains several steps inside it. Now with the schedule it runs very frequently and more than 100 jobs are running almost simulteneously. so I want to limit the number of jobs running at a time say at a time I want to run 10 jobs after that other 10 set and s
How can I do it help me ou
Regards
SunilYou can adapt schedules, or you can create a wrapper job. This wrapper job
can start other jobs on each own step using the sp_start_job system SP.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:9250860D-15DE-408D-A5A8-3CA7FAD56CC4@.microsoft.com...
> I have created several jobs which contains several steps inside it. Now
with the schedule it runs very frequently and more than 100 jobs are running
almost simulteneously. so I want to limit the number of jobs running at a
time say at a time I want to run 10 jobs after that other 10 set and so
>
> How can I do it help me out
> Regards,
> Sunil

Jobs

I have created several jobs which contains several steps inside it. Now with
the schedule it runs very frequently and more than 100 jobs are running alm
ost simulteneously. so I want to limit the number of jobs running at a time
say at a time I want to run
10 jobs after that other 10 set and so
How can I do it help me out
Regards,
SunilYou can adapt schedules, or you can create a wrapper job. This wrapper job
can start other jobs on each own step using the sp_start_job system SP.
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:9250860D-15DE-408D-A5A8-3CA7FAD56CC4@.microsoft.com...

quote:

---

> I have created several jobs which contains several steps inside it. Now

---

with the schedule it runs very frequently and more than 100 jobs are running
almost simulteneously. so I want to limit the number of jobs running at a
time say at a time I want to run 10 jobs after that other 10 set and so

quote:

---

>
> How can I do it help me out
> Regards,
> Sunil

---

Job with steps problem

Hi all,
I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest sp
on one machine.
In SQL2005 I have created 2 maintenance plans - one for 2005 and second for
2000
Also created 3rd job (first 2 were generated by maintenance plans) with the
following steps:
1. cmd to move filese from A to B
2. SQL SISP package \Maintenance Plans\2005
3. SQL SISP package \Maintenance Plans\2000
When I execute that job it goes to step one and move those file, it's ok.
But step 2 and 3 are not executed correctly, I mean they are executed
(Successful) but that maintenance plan is not executing. After all I'm
getting the successful result but no backup are mage
Tried to execute those maintenance plans one by one. 2000 - successful but
nothing happens, the same is for 2005
When I execute the job associated - all is ok.
How could I add defined JOB to the Job Steps, to make it all run?
Thank you in advance
Alex
I don't think it is a good idea to call job from another job's step.
I mean you have to be certain that it is really business requirements
Take a look at sp_start_job system stored procedure in the BOL
"Guzun, Alex" <a> wrote in message
news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
> Hi all,
> I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest
> sp on one machine.
> In SQL2005 I have created 2 maintenance plans - one for 2005 and second
> for 2000
> Also created 3rd job (first 2 were generated by maintenance plans) with
> the following steps:
> 1. cmd to move filese from A to B
> 2. SQL SISP package \Maintenance Plans\2005
> 3. SQL SISP package \Maintenance Plans\2000
> When I execute that job it goes to step one and move those file, it's ok.
> But step 2 and 3 are not executed correctly, I mean they are executed
> (Successful) but that maintenance plan is not executing. After all I'm
> getting the successful result but no backup are mage
> Tried to execute those maintenance plans one by one. 2000 - successful but
> nothing happens, the same is for 2005
> When I execute the job associated - all is ok.
> How could I add defined JOB to the Job Steps, to make it all run?
> Thank you in advance
|||Hm... don't know what is BOL, and how to use sp_start_job system stored
procedure
I'm just a guy that using GUI for SQL
I need to achieve those job to run as 1, 2, 3.
2nd will wait for 1, to end and so on
Please help me if you can
Thanks in advance
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:#jzRXGhvHHA.2288@.TK2MSFTNGP05.phx.gbl...
> Alex
> I don't think it is a good idea to call job from another job's step.
> I mean you have to be certain that it is really business requirements
> Take a look at sp_start_job system stored procedure in the BOL
>
> "Guzun, Alex" <a> wrote in message
> news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
>
>
|||Alex
BOL -Books On Line that is a part of SQL Server Client Tools installation.
Can you create three jobs and and checking the status by using sp_help_job?
"Guzun, Alex" <a> wrote in message
news:%23tGvRWjvHHA.1168@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Hm... don't know what is BOL, and how to use sp_start_job system stored
> procedure
> I'm just a guy that using GUI for SQL
> I need to achieve those job to run as 1, 2, 3.
> 2nd will wait for 1, to end and so on
> Please help me if you can
> Thanks in advance
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:#jzRXGhvHHA.2288@.TK2MSFTNGP05.phx.gbl...
|||Sorry
I have 2 jobs for 2 maintenance plans
Got also 3 job with cmd script to move files from DAY folder to WEEK folder
And everyday I'll tape DAY folder
Now I want them to run one by one, don't want to calculate time intervals
for each one
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:#DnGyajvHHA.1164@.TK2MSFTNGP02.phx.gbl...
> Alex
> BOL -Books On Line that is a part of SQL Server Client Tools installation.
> Can you create three jobs and and checking the status by using
> sp_help_job?
>
> "Guzun, Alex" <a> wrote in message
> news:%23tGvRWjvHHA.1168@.TK2MSFTNGP02.phx.gbl...
>

Job with steps problem

Hi all,
I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest sp
on one machine.
In SQL2005 I have created 2 maintenance plans - one for 2005 and second for
2000
Also created 3rd job (first 2 were generated by maintenance plans) with the
following steps:
1. cmd to move filese from A to B
2. SQL SISP package \Maintenance Plans\2005
3. SQL SISP package \Maintenance Plans\2000
When I execute that job it goes to step one and move those file, it's ok.
But step 2 and 3 are not executed correctly, I mean they are executed
(Successful) but that maintenance plan is not executing. After all I'm
getting the successful result but no backup are mage :(
Tried to execute those maintenance plans one by one. 2000 - successful but
nothing happens, the same is for 2005
When I execute the job associated - all is ok.
How could I add defined JOB to the Job Steps, to make it all run?
Thank you in advanceAlex
I don't think it is a good idea to call job from another job's step.
I mean you have to be certain that it is really business requirements
Take a look at sp_start_job system stored procedure in the BOL
"Guzun, Alex" <a> wrote in message
news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
> Hi all,
> I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest
> sp on one machine.
> In SQL2005 I have created 2 maintenance plans - one for 2005 and second
> for 2000
> Also created 3rd job (first 2 were generated by maintenance plans) with
> the following steps:
> 1. cmd to move filese from A to B
> 2. SQL SISP package \Maintenance Plans\2005
> 3. SQL SISP package \Maintenance Plans\2000
> When I execute that job it goes to step one and move those file, it's ok.
> But step 2 and 3 are not executed correctly, I mean they are executed
> (Successful) but that maintenance plan is not executing. After all I'm
> getting the successful result but no backup are mage :(
> Tried to execute those maintenance plans one by one. 2000 - successful but
> nothing happens, the same is for 2005
> When I execute the job associated - all is ok.
> How could I add defined JOB to the Job Steps, to make it all run?
> Thank you in advance|||Hm... don't know what is BOL, and how to use sp_start_job system stored
procedure
I'm just a guy that using GUI for SQL
I need to achieve those job to run as 1, 2, 3.
2nd will wait for 1, to end and so on :(
Please help me if you can
Thanks in advance
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:#jzRXGhvHHA.2288@.TK2MSFTNGP05.phx.gbl...
> Alex
> I don't think it is a good idea to call job from another job's step.
> I mean you have to be certain that it is really business requirements
> Take a look at sp_start_job system stored procedure in the BOL
>
> "Guzun, Alex" <a> wrote in message
> news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
>> Hi all,
>> I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest
>> sp on one machine.
>> In SQL2005 I have created 2 maintenance plans - one for 2005 and second
>> for 2000
>> Also created 3rd job (first 2 were generated by maintenance plans) with
>> the following steps:
>> 1. cmd to move filese from A to B
>> 2. SQL SISP package \Maintenance Plans\2005
>> 3. SQL SISP package \Maintenance Plans\2000
>> When I execute that job it goes to step one and move those file, it's ok.
>> But step 2 and 3 are not executed correctly, I mean they are executed
>> (Successful) but that maintenance plan is not executing. After all I'm
>> getting the successful result but no backup are mage :(
>> Tried to execute those maintenance plans one by one. 2000 - successful
>> but nothing happens, the same is for 2005
>> When I execute the job associated - all is ok.
>> How could I add defined JOB to the Job Steps, to make it all run?
>> Thank you in advance
>
>|||Alex
BOL -Books On Line that is a part of SQL Server Client Tools installation.
Can you create three jobs and and checking the status by using sp_help_job?
"Guzun, Alex" <a> wrote in message
news:%23tGvRWjvHHA.1168@.TK2MSFTNGP02.phx.gbl...
> Hm... don't know what is BOL, and how to use sp_start_job system stored
> procedure
> I'm just a guy that using GUI for SQL
> I need to achieve those job to run as 1, 2, 3.
> 2nd will wait for 1, to end and so on :(
> Please help me if you can
> Thanks in advance
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:#jzRXGhvHHA.2288@.TK2MSFTNGP05.phx.gbl...
>> Alex
>> I don't think it is a good idea to call job from another job's step.
>> I mean you have to be certain that it is really business requirements
>> Take a look at sp_start_job system stored procedure in the BOL
>>
>> "Guzun, Alex" <a> wrote in message
>> news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
>> Hi all,
>> I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest
>> sp on one machine.
>> In SQL2005 I have created 2 maintenance plans - one for 2005 and second
>> for 2000
>> Also created 3rd job (first 2 were generated by maintenance plans) with
>> the following steps:
>> 1. cmd to move filese from A to B
>> 2. SQL SISP package \Maintenance Plans\2005
>> 3. SQL SISP package \Maintenance Plans\2000
>> When I execute that job it goes to step one and move those file, it's
>> ok. But step 2 and 3 are not executed correctly, I mean they are
>> executed (Successful) but that maintenance plan is not executing. After
>> all I'm getting the successful result but no backup are mage :(
>> Tried to execute those maintenance plans one by one. 2000 - successful
>> but nothing happens, the same is for 2005
>> When I execute the job associated - all is ok.
>> How could I add defined JOB to the Job Steps, to make it all run?
>> Thank you in advance
>>|||Sorry :)
I have 2 jobs for 2 maintenance plans
Got also 3 job with cmd script to move files from DAY folder to WEEK folder
And everyday I'll tape DAY folder
Now I want them to run one by one, don't want to calculate time intervals
for each one
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:#DnGyajvHHA.1164@.TK2MSFTNGP02.phx.gbl...
> Alex
> BOL -Books On Line that is a part of SQL Server Client Tools installation.
> Can you create three jobs and and checking the status by using
> sp_help_job?
>
> "Guzun, Alex" <a> wrote in message
> news:%23tGvRWjvHHA.1168@.TK2MSFTNGP02.phx.gbl...
>> Hm... don't know what is BOL, and how to use sp_start_job system stored
>> procedure
>> I'm just a guy that using GUI for SQL
>> I need to achieve those job to run as 1, 2, 3.
>> 2nd will wait for 1, to end and so on :(
>> Please help me if you can
>> Thanks in advance
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:#jzRXGhvHHA.2288@.TK2MSFTNGP05.phx.gbl...
>> Alex
>> I don't think it is a good idea to call job from another job's step.
>> I mean you have to be certain that it is really business requirements
>> Take a look at sp_start_job system stored procedure in the BOL
>>
>> "Guzun, Alex" <a> wrote in message
>> news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
>> Hi all,
>> I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000
>> latest sp on one machine.
>> In SQL2005 I have created 2 maintenance plans - one for 2005 and second
>> for 2000
>> Also created 3rd job (first 2 were generated by maintenance plans) with
>> the following steps:
>> 1. cmd to move filese from A to B
>> 2. SQL SISP package \Maintenance Plans\2005
>> 3. SQL SISP package \Maintenance Plans\2000
>> When I execute that job it goes to step one and move those file, it's
>> ok. But step 2 and 3 are not executed correctly, I mean they are
>> executed (Successful) but that maintenance plan is not executing. After
>> all I'm getting the successful result but no backup are mage :(
>> Tried to execute those maintenance plans one by one. 2000 - successful
>> but nothing happens, the same is for 2005
>> When I execute the job associated - all is ok.
>> How could I add defined JOB to the Job Steps, to make it all run?
>> Thank you in advance
>>
>

Job with steps problem

Hi all,
I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest sp
on one machine.
In SQL2005 I have created 2 maintenance plans - one for 2005 and second for
2000
Also created 3rd job (first 2 were generated by maintenance plans) with the
following steps:
1. cmd to move filese from A to B
2. SQL SISP package \Maintenance Plans\2005
3. SQL SISP package \Maintenance Plans\2000
When I execute that job it goes to step one and move those file, it's ok.
But step 2 and 3 are not executed correctly, I mean they are executed
(Successful) but that maintenance plan is not executing. After all I'm
getting the successful result but no backup are mage
Tried to execute those maintenance plans one by one. 2000 - successful but
nothing happens, the same is for 2005
When I execute the job associated - all is ok.
How could I add defined JOB to the Job Steps, to make it all run?
Thank you in advanceAlex
I don't think it is a good idea to call job from another job's step.
I mean you have to be certain that it is really business requirements
Take a look at sp_start_job system stored procedure in the BOL
"Guzun, Alex" <a> wrote in message
news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
> Hi all,
> I have Windows 2003 r2 Server x64, sql 2005 sp1 x64 with sql 2000 latest
> sp on one machine.
> In SQL2005 I have created 2 maintenance plans - one for 2005 and second
> for 2000
> Also created 3rd job (first 2 were generated by maintenance plans) with
> the following steps:
> 1. cmd to move filese from A to B
> 2. SQL SISP package \Maintenance Plans\2005
> 3. SQL SISP package \Maintenance Plans\2000
> When I execute that job it goes to step one and move those file, it's ok.
> But step 2 and 3 are not executed correctly, I mean they are executed
> (Successful) but that maintenance plan is not executing. After all I'm
> getting the successful result but no backup are mage
> Tried to execute those maintenance plans one by one. 2000 - successful but
> nothing happens, the same is for 2005
> When I execute the job associated - all is ok.
> How could I add defined JOB to the Job Steps, to make it all run?
> Thank you in advance|||Hm... don't know what is BOL, and how to use sp_start_job system stored
procedure
I'm just a guy that using GUI for SQL
I need to achieve those job to run as 1, 2, 3.
2nd will wait for 1, to end and so on
Please help me if you can
Thanks in advance
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:#jzRXGhvHHA.2288@.TK2MSFTNGP05.phx.gbl...
> Alex
> I don't think it is a good idea to call job from another job's step.
> I mean you have to be certain that it is really business requirements
> Take a look at sp_start_job system stored procedure in the BOL
>
> "Guzun, Alex" <a> wrote in message
> news:OT%23pG$gvHHA.536@.TK2MSFTNGP06.phx.gbl...
>
>|||Alex
BOL -Books On Line that is a part of SQL Server Client Tools installation.
Can you create three jobs and and checking the status by using sp_help_job?
"Guzun, Alex" <a> wrote in message
news:%23tGvRWjvHHA.1168@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Hm... don't know what is BOL, and how to use sp_start_job system stored
> procedure
> I'm just a guy that using GUI for SQL
> I need to achieve those job to run as 1, 2, 3.
> 2nd will wait for 1, to end and so on
> Please help me if you can
> Thanks in advance
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:#jzRXGhvHHA.2288@.TK2MSFTNGP05.phx.gbl...|||Sorry
I have 2 jobs for 2 maintenance plans
Got also 3 job with cmd script to move files from DAY folder to WEEK folder
And everyday I'll tape DAY folder
Now I want them to run one by one, don't want to calculate time intervals
for each one
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:#DnGyajvHHA.1164@.TK2MSFTNGP02.phx.gbl...
> Alex
> BOL -Books On Line that is a part of SQL Server Client Tools installation.
> Can you create three jobs and and checking the status by using
> sp_help_job?
>
> "Guzun, Alex" <a> wrote in message
> news:%23tGvRWjvHHA.1168@.TK2MSFTNGP02.phx.gbl...
>

Job View History is disappearing

I've created new maintenance plans and while I can view the maintenance plan
history, the job view history is deleted somehow. Where is this controlled?
The maintenance plan is not deleting job history and I don't see any other
jobs or maintenance plans that are deleting history.
This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
the job history, but I don't see that in 2005. Is there a default somewhere
I'm missing?
Thanks
RonRon,
In SSMS, right-click on SQL Agent, select Properties, go to the History
page. This is where you can set the size of history.
RLF
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:0EB1F324-BF2B-4F24-87AC-585FAB4071E3@.microsoft.com...
> I've created new maintenance plans and while I can view the maintenance
> plan
> history, the job view history is deleted somehow. Where is this
> controlled?
> The maintenance plan is not deleting job history and I don't see any
> other
> jobs or maintenance plans that are deleting history.
> This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
> the job history, but I don't see that in 2005. Is there a default
> somewhere
> I'm missing?
> Thanks
> Ron|||Thanks - I'll bump it up and see if that's the issue.
"Russell Fields" wrote:
> Ron,
> In SSMS, right-click on SQL Agent, select Properties, go to the History
> page. This is where you can set the size of history.
> RLF
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:0EB1F324-BF2B-4F24-87AC-585FAB4071E3@.microsoft.com...
> > I've created new maintenance plans and while I can view the maintenance
> > plan
> > history, the job view history is deleted somehow. Where is this
> > controlled?
> > The maintenance plan is not deleting job history and I don't see any
> > other
> > jobs or maintenance plans that are deleting history.
> >
> > This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
> > the job history, but I don't see that in 2005. Is there a default
> > somewhere
> > I'm missing?
> >
> > Thanks
> >
> > Ron
>
>

Job Scheduling

How do I schedule the jobs to run in sequence? I have created a package to
call the sql server agent jobs in sequence but looks like all the jobs are
running at the same time, not waiting for the other jobs to complete. I did
put the constriants not to run the second job until the first job is
complete. But still it is not behaving as instructed.
Any thoughts,
Thanks,
MariJobs run asynchronously and independently of each other.
You need to make ONE job and call each "job" as an individual step. That
way, "job"/step 2 will not start until "job"/step 1 is complete (and you can
terminate the whole sequence on an individual step failure, or you can have
individual step failures ignored and just move to the next step).
"Maria" <Maria@.discussions.microsoft.com> wrote in message
news:B7B1BBAC-F54E-48C6-A871-A9FBFE1BB0C2@.microsoft.com...
> How do I schedule the jobs to run in sequence? I have created a package to
> call the sql server agent jobs in sequence but looks like all the jobs are
> running at the same time, not waiting for the other jobs to complete. I
> did
> put the constriants not to run the second job until the first job is
> complete. But still it is not behaving as instructed.
> Any thoughts,
> Thanks,
> Mari|||Thank you Aaron. But there is no option to define the "type" for sql server
Agent jobs to call the another job. I guess you know what I am talking.
When I am creating the 'job', for the step 1, there is no Agent Jobs
options. We have only IS package or AS or activeX etc., but not the agent
jobs : (
Tks
"Aaron Bertrand [SQL Server MVP]" wrote:

> Jobs run asynchronously and independently of each other.
> You need to make ONE job and call each "job" as an individual step. That
> way, "job"/step 2 will not start until "job"/step 1 is complete (and you c
an
> terminate the whole sequence on an individual step failure, or you can hav
e
> individual step failures ignored and just move to the next step).
>
> "Maria" <Maria@.discussions.microsoft.com> wrote in message
> news:B7B1BBAC-F54E-48C6-A871-A9FBFE1BB0C2@.microsoft.com...
>
>|||If you are using SQL Server 2005, Service Broker can be used to guarantee
in-order execution:
http://www.microsoft.com/technet/te...lt.a
spx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Maria" <Maria@.discussions.microsoft.com> wrote in message
news:B7B1BBAC-F54E-48C6-A871-A9FBFE1BB0C2@.microsoft.com...
> How do I schedule the jobs to run in sequence? I have created a package to
> call the sql server agent jobs in sequence but looks like all the jobs are
> running at the same time, not waiting for the other jobs to complete. I
> did
> put the constriants not to run the second job until the first job is
> complete. But still it is not behaving as instructed.
> Any thoughts,
> Thanks,
> Mari|||Maria wrote:
> How do I schedule the jobs to run in sequence? I have created a package to
> call the sql server agent jobs in sequence but looks like all the jobs are
> running at the same time, not waiting for the other jobs to complete. I di
d
> put the constriants not to run the second job until the first job is
> complete. But still it is not behaving as instructed.
> Any thoughts,
> Thanks,
> Mari
Are you referring to SQL Agent jobs, or tasks within a DTS package?|||It is "Execute SQL Server Agent Job Task" under Maintenance Plan Tasks for a
DTS package.
"Tracy McKibben" wrote:

> Maria wrote:
> Are you referring to SQL Agent jobs, or tasks within a DTS package?
>|||Maria wrote:
> It is "Execute SQL Server Agent Job Task" under Maintenance Plan Tasks for
a
> DTS package.
>
I'm not familiar with that one. So, you're using a DTS package to
execute Maintenance Plan tasks. Is the DTS package then going to be
scheduled to run via SQL Agent? Seems sorta bass-ackwards... Am I
completely not understanding what you're trying to accomplish?|||I think your understanding is right. But looks like that doesn't work. When
I
created the package to run all these jobs in a sequence, all thejobs are
running at the same time though I put constraints on it.
Hope this is clear.
thanks
"Tracy McKibben" wrote:

> Maria wrote:
> I'm not familiar with that one. So, you're using a DTS package to
> execute Maintenance Plan tasks. Is the DTS package then going to be
> scheduled to run via SQL Agent? Seems sorta bass-ackwards... Am I
> completely not understanding what you're trying to accomplish?
>|||Hi Roger,
I never used the Broker Service. Could you give some more details how to use
this service to schedule batch jobs.
Thanks
"Roger Wolter[MSFT]" wrote:

> If you are using SQL Server 2005, Service Broker can be used to guarantee
> in-order execution:
> http://www.microsoft.com/technet/te...lt
.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Maria" <Maria@.discussions.microsoft.com> wrote in message
> news:B7B1BBAC-F54E-48C6-A871-A9FBFE1BB0C2@.microsoft.com...
>
>|||Maria wrote:
> I think your understanding is right. But looks like that doesn't work. Whe
n I
> created the package to run all these jobs in a sequence, all thejobs are
> running at the same time though I put constraints on it.
>
Ok... Well, that leads me to ask, why not just let the maintenance plan
schedule the jobs in SQL Agent like it's supposed to, instead of
wrapping them in a DTS package like this?
I'll go one step further, and suggest that you dump the maintenance plan
altogether, and write your own processes to do what the maintenance plan
offers you. Write your own BACKUP job, write your own index maintenance
routine, don't shrink your databases. You'll learn alot more about your
environment by doing so...sql

Job runs succesfully, but database not updated

I have created a job to run an executable. This executable has to read an
Excelsheet in order to import the data into the database.
I got the message that the job has run succesfully, but the data is not in
the database.
My job looks like this:
c:\mydirectory\bin\excelimport.exe /Slocal) /D:DataComp 20051020
S: --> the local server
D:--> database name
Thank you for your help.
Kind regards,
LoHi
You don't say where the job expects the excel file to be! Have you looks at
SQL profiler to see what is happening when the program runs?
John
"lo" wrote:

> I have created a job to run an executable. This executable has to read an
> Excelsheet in order to import the data into the database.
> I got the message that the job has run succesfully, but the data is not in
> the database.
> My job looks like this:
> c:\mydirectory\bin\excelimport.exe /Slocal) /D:DataComp 20051020
> S: --> the local server
> D:--> database name
> --
> Thank you for your help.
> Kind regards,
> Lo|||I have run the profiler, but here as well I get no error message once or eve
r.
I have updated the string like this
c:\mydirectory\bin\excelimport.exe /Slocal) /D:[DataComp 20051020]
The path to the excel sheet is in the excelimport.exe.
Do you have any other idea'
Thank you for your help.
Kind regards,
Lo
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You don't say where the job expects the excel file to be! Have you looks a
t
> SQL profiler to see what is happening when the program runs?
> John
> "lo" wrote:
>|||Hi
I would not expect any error messages from SQL Profile, just the information
about which database it is running against and what SQL statements are being
executed by the job. You can then confirm that it is not connecting to the
correct database or that it is not finding the file.
Do you have a dynamic properties task to change the destination database?
You may want to see http://www.sqldts.com/default.aspx?252
John
"lo" wrote:
[vbcol=seagreen]
> I have run the profiler, but here as well I get no error message once or e
ver.
> I have updated the string like this
> c:\mydirectory\bin\excelimport.exe /Slocal) /D:[DataComp 20051020]
> The path to the excel sheet is in the excelimport.exe.
> Do you have any other idea'
>
> --
> Thank you for your help.
> Kind regards,
> Lo
>
> "John Bell" wrote:
>

Job runs succesfully, but database not updated

I have created a job to run an executable. This executable has to read an
Excelsheet in order to import the data into the database.
I got the message that the job has run succesfully, but the data is not in
the database.
My job looks like this:
c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
S: --> the local server
D:--> database name
--
Thank you for your help.
Kind regards,
LoHi
You don't say where the job expects the excel file to be! Have you looks at
SQL profiler to see what is happening when the program runs?
John
"lo" wrote:
> I have created a job to run an executable. This executable has to read an
> Excelsheet in order to import the data into the database.
> I got the message that the job has run succesfully, but the data is not in
> the database.
> My job looks like this:
> c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> S: --> the local server
> D:--> database name
> --
> Thank you for your help.
> Kind regards,
> Lo|||I have run the profiler, but here as well I get no error message once or ever.
I have updated the string like this
c:\mydirectory\bin\excelimport.exe /S:(local) /D:[DataComp 20051020]
The path to the excel sheet is in the excelimport.exe.
Do you have any other idea'
Thank you for your help.
Kind regards,
Lo
"John Bell" wrote:
> Hi
> You don't say where the job expects the excel file to be! Have you looks at
> SQL profiler to see what is happening when the program runs?
> John
> "lo" wrote:
> > I have created a job to run an executable. This executable has to read an
> > Excelsheet in order to import the data into the database.
> > I got the message that the job has run succesfully, but the data is not in
> > the database.
> > My job looks like this:
> > c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> > S: --> the local server
> > D:--> database name
> >
> > --
> > Thank you for your help.
> >
> > Kind regards,
> >
> > Lo|||Hi
I would not expect any error messages from SQL Profile, just the information
about which database it is running against and what SQL statements are being
executed by the job. You can then confirm that it is not connecting to the
correct database or that it is not finding the file.
Do you have a dynamic properties task to change the destination database?
You may want to see http://www.sqldts.com/default.aspx?252
John
"lo" wrote:
> I have run the profiler, but here as well I get no error message once or ever.
> I have updated the string like this
> c:\mydirectory\bin\excelimport.exe /S:(local) /D:[DataComp 20051020]
> The path to the excel sheet is in the excelimport.exe.
> Do you have any other idea'
>
> --
> Thank you for your help.
> Kind regards,
> Lo
>
> "John Bell" wrote:
> > Hi
> >
> > You don't say where the job expects the excel file to be! Have you looks at
> > SQL profiler to see what is happening when the program runs?
> >
> > John
> >
> > "lo" wrote:
> >
> > > I have created a job to run an executable. This executable has to read an
> > > Excelsheet in order to import the data into the database.
> > > I got the message that the job has run succesfully, but the data is not in
> > > the database.
> > > My job looks like this:
> > > c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> > > S: --> the local server
> > > D:--> database name
> > >
> > > --
> > > Thank you for your help.
> > >
> > > Kind regards,
> > >
> > > Lo

Job reports failure, but bak file created

The view history of a job created from a maintenance plan reports that it
failed, and the log says that it failed in the backup operation because
"A nonrecoverable I/O error occurred on file
"\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:" 64(The specified network name is no longer available.).
And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was a
valid backup, as I just confirmed by restoring it to a test database. So why
the error?
Also, this does not happen consistently. The reporting of this apparent
non-error has occured twice out of the last five runs.Does the backup process include a Verify? IF so the error is most likely
occurring on the verify process which is done after the backup is complete.
Backup & Verify is an intensive operation and if you are backing up across
the network there is plenty of time for the network to drop packets etc.
Sounds like you have an unstable network or networks equipment.
--
Andrew J. Kelly SQL MVP
"Bev Kaufman" <BevKaufman@.discussions.microsoft.com> wrote in message
news:AF302871-2972-420D-A932-408F42EA1EA9@.microsoft.com...
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:"
> 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was
> a
> valid backup, as I just confirmed by restoring it to a test database. So
> why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.|||On Jul 11, 9:16 am, Bev Kaufman <BevKauf...@.discussions.microsoft.com>
wrote:
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707=11=AD0001.bak:" 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it wa=s a
> valid backup, as I just confirmed by restoring it to a test database. So= why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.
Are you utilizing a third party backup tool? We use RedGate in our
SQL Server 2000 (SP3a - don't ask) environment and have encountered
this on a daily basis. When we used normal backup procedures, no
errors were reported. I have the same issue though, but figured it
might be resolved with a newer service pack. The only thing I can
think of is possibly disk contention of you are utilizing a SAN
environment, but not sure.
Maybe if we put our heads together, we can figure it out. I haven't
put a whole lot of effort into it once I realized that the backups are
working properly (as verified by the restores). I know, terrible, but
sometimes other fires are hotter :)

Job not running as owner

Here's a weird one.
I've got a job on one server, owner 'sa'. It runs fine. I created the
same job on another server, still with owner 'sa', and it fails. When I
view the history, it fails because it's running as a different user,
one without the necessary rights. On the server that it works on, the
job is being run as the correct user, 'sa'.
In the step, under advanced, 'Run as user:' is set to '(self)', just as
it is in the server that works.
Help! I cannot see any difference between the jobs on the 2 servers,
and I can't think of any reason why it's trying to execute the job as a
user other than the owner.
Hi,
Have a look into the SQL Agent startup account. See if it have necessary
rights.
Thanks
Hari
SQL Server MVP
<ben.bawden@.btopenworld.com> wrote in message
news:1129111265.698508.242580@.g43g2000cwa.googlegr oups.com...
> Here's a weird one.
> I've got a job on one server, owner 'sa'. It runs fine. I created the
> same job on another server, still with owner 'sa', and it fails. When I
> view the history, it fails because it's running as a different user,
> one without the necessary rights. On the server that it works on, the
> job is being run as the correct user, 'sa'.
> In the step, under advanced, 'Run as user:' is set to '(self)', just as
> it is in the server that works.
> Help! I cannot see any difference between the jobs on the 2 servers,
> and I can't think of any reason why it's trying to execute the job as a
> user other than the owner.
>
|||Check *both* the job as a whole and each jobstep. Job should be owned by "sa" and job step should be
<self>. Double and triple check.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<ben.bawden@.btopenworld.com> wrote in message
news:1129111265.698508.242580@.g43g2000cwa.googlegr oups.com...
> Here's a weird one.
> I've got a job on one server, owner 'sa'. It runs fine. I created the
> same job on another server, still with owner 'sa', and it fails. When I
> view the history, it fails because it's running as a different user,
> one without the necessary rights. On the server that it works on, the
> job is being run as the correct user, 'sa'.
> In the step, under advanced, 'Run as user:' is set to '(self)', just as
> it is in the server that works.
> Help! I cannot see any difference between the jobs on the 2 servers,
> and I can't think of any reason why it's trying to execute the job as a
> user other than the owner.
>
|||Hi. The SQL Server Agent startup account is the same on both servers.
However server1 is running the job as sa, and server2 is running the
job as the SQL Server Agent startup account. Strange.
I've double, triple, quadruple checked that the job in question is set
to owner sa and the step is set to self.
Other jobs on the server are also running as the non-sa account, but
this one is the only one that's failing, because it's running through a
linked server. As a work around I've built a DTS package that runs the
task, and then scheduled that DTS package, but I'd really like to
understand why this server is running jobs under the non-sa account.
|||I'm not sure whether you are talking about TSQL or CmdExec job step. However, two things to check:
1 EM, Agent, right-click, properties, right-most tab. Check how agent log on to SQL Server.
2 Security mode for each SQL Server (Windows only or mixed).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<ben.bawden@.btopenworld.com> wrote in message
news:1129115237.379149.269800@.g43g2000cwa.googlegr oups.com...
> Hi. The SQL Server Agent startup account is the same on both servers.
> However server1 is running the job as sa, and server2 is running the
> job as the SQL Server Agent startup account. Strange.
> I've double, triple, quadruple checked that the job in question is set
> to owner sa and the step is set to self.
> Other jobs on the server are also running as the non-sa account, but
> this one is the only one that's failing, because it's running through a
> linked server. As a work around I've built a DTS package that runs the
> task, and then scheduled that DTS package, but I'd really like to
> understand why this server is running jobs under the non-sa account.
>
sql

Job not running as owner

Here's a weird one.
I've got a job on one server, owner 'sa'. It runs fine. I created the
same job on another server, still with owner 'sa', and it fails. When I
view the history, it fails because it's running as a different user,
one without the necessary rights. On the server that it works on, the
job is being run as the correct user, 'sa'.
In the step, under advanced, 'Run as user:' is set to '(self)', just as
it is in the server that works.
Help! I cannot see any difference between the jobs on the 2 servers,
and I can't think of any reason why it's trying to execute the job as a
user other than the owner.Hi,
Have a look into the SQL Agent startup account. See if it have necessary
rights.
Thanks
Hari
SQL Server MVP
<ben.bawden@.btopenworld.com> wrote in message
news:1129111265.698508.242580@.g43g2000cwa.googlegroups.com...
> Here's a weird one.
> I've got a job on one server, owner 'sa'. It runs fine. I created the
> same job on another server, still with owner 'sa', and it fails. When I
> view the history, it fails because it's running as a different user,
> one without the necessary rights. On the server that it works on, the
> job is being run as the correct user, 'sa'.
> In the step, under advanced, 'Run as user:' is set to '(self)', just as
> it is in the server that works.
> Help! I cannot see any difference between the jobs on the 2 servers,
> and I can't think of any reason why it's trying to execute the job as a
> user other than the owner.
>|||Check *both* the job as a whole and each jobstep. Job should be owned by "sa
" and job step should be
<self>. Double and triple check.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<ben.bawden@.btopenworld.com> wrote in message
news:1129111265.698508.242580@.g43g2000cwa.googlegroups.com...
> Here's a weird one.
> I've got a job on one server, owner 'sa'. It runs fine. I created the
> same job on another server, still with owner 'sa', and it fails. When I
> view the history, it fails because it's running as a different user,
> one without the necessary rights. On the server that it works on, the
> job is being run as the correct user, 'sa'.
> In the step, under advanced, 'Run as user:' is set to '(self)', just as
> it is in the server that works.
> Help! I cannot see any difference between the jobs on the 2 servers,
> and I can't think of any reason why it's trying to execute the job as a
> user other than the owner.
>|||Hi. The SQL Server Agent startup account is the same on both servers.
However server1 is running the job as sa, and server2 is running the
job as the SQL Server Agent startup account. Strange.
I've double, triple, quadruple checked that the job in question is set
to owner sa and the step is set to self.
Other jobs on the server are also running as the non-sa account, but
this one is the only one that's failing, because it's running through a
linked server. As a work around I've built a DTS package that runs the
task, and then scheduled that DTS package, but I'd really like to
understand why this server is running jobs under the non-sa account.|||I'm not sure whether you are talking about TSQL or CmdExec job step. However
, two things to check:
1 EM, Agent, right-click, properties, right-most tab. Check how agent log on
to SQL Server.
2 Security mode for each SQL Server (Windows only or mixed).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<ben.bawden@.btopenworld.com> wrote in message
news:1129115237.379149.269800@.g43g2000cwa.googlegroups.com...
> Hi. The SQL Server Agent startup account is the same on both servers.
> However server1 is running the job as sa, and server2 is running the
> job as the SQL Server Agent startup account. Strange.
> I've double, triple, quadruple checked that the job in question is set
> to owner sa and the step is set to self.
> Other jobs on the server are also running as the non-sa account, but
> this one is the only one that's failing, because it's running through a
> linked server. As a work around I've built a DTS package that runs the
> task, and then scheduled that DTS package, but I'd really like to
> understand why this server is running jobs under the non-sa account.
>

Job not running as owner

Here's a weird one.
I've got a job on one server, owner 'sa'. It runs fine. I created the
same job on another server, still with owner 'sa', and it fails. When I
view the history, it fails because it's running as a different user,
one without the necessary rights. On the server that it works on, the
job is being run as the correct user, 'sa'.
In the step, under advanced, 'Run as user:' is set to '(self)', just as
it is in the server that works.
Help! I cannot see any difference between the jobs on the 2 servers,
and I can't think of any reason why it's trying to execute the job as a
user other than the owner.Hi,
Have a look into the SQL Agent startup account. See if it have necessary
rights.
Thanks
Hari
SQL Server MVP
<ben.bawden@.btopenworld.com> wrote in message
news:1129111265.698508.242580@.g43g2000cwa.googlegroups.com...
> Here's a weird one.
> I've got a job on one server, owner 'sa'. It runs fine. I created the
> same job on another server, still with owner 'sa', and it fails. When I
> view the history, it fails because it's running as a different user,
> one without the necessary rights. On the server that it works on, the
> job is being run as the correct user, 'sa'.
> In the step, under advanced, 'Run as user:' is set to '(self)', just as
> it is in the server that works.
> Help! I cannot see any difference between the jobs on the 2 servers,
> and I can't think of any reason why it's trying to execute the job as a
> user other than the owner.
>|||Check *both* the job as a whole and each jobstep. Job should be owned by "sa" and job step should be
<self>. Double and triple check.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<ben.bawden@.btopenworld.com> wrote in message
news:1129111265.698508.242580@.g43g2000cwa.googlegroups.com...
> Here's a weird one.
> I've got a job on one server, owner 'sa'. It runs fine. I created the
> same job on another server, still with owner 'sa', and it fails. When I
> view the history, it fails because it's running as a different user,
> one without the necessary rights. On the server that it works on, the
> job is being run as the correct user, 'sa'.
> In the step, under advanced, 'Run as user:' is set to '(self)', just as
> it is in the server that works.
> Help! I cannot see any difference between the jobs on the 2 servers,
> and I can't think of any reason why it's trying to execute the job as a
> user other than the owner.
>|||Hi. The SQL Server Agent startup account is the same on both servers.
However server1 is running the job as sa, and server2 is running the
job as the SQL Server Agent startup account. Strange.
I've double, triple, quadruple checked that the job in question is set
to owner sa and the step is set to self.
Other jobs on the server are also running as the non-sa account, but
this one is the only one that's failing, because it's running through a
linked server. As a work around I've built a DTS package that runs the
task, and then scheduled that DTS package, but I'd really like to
understand why this server is running jobs under the non-sa account.|||I'm not sure whether you are talking about TSQL or CmdExec job step. However, two things to check:
1 EM, Agent, right-click, properties, right-most tab. Check how agent log on to SQL Server.
2 Security mode for each SQL Server (Windows only or mixed).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<ben.bawden@.btopenworld.com> wrote in message
news:1129115237.379149.269800@.g43g2000cwa.googlegroups.com...
> Hi. The SQL Server Agent startup account is the same on both servers.
> However server1 is running the job as sa, and server2 is running the
> job as the SQL Server Agent startup account. Strange.
> I've double, triple, quadruple checked that the job in question is set
> to owner sa and the step is set to self.
> Other jobs on the server are also running as the non-sa account, but
> this one is the only one that's failing, because it's running through a
> linked server. As a work around I've built a DTS package that runs the
> task, and then scheduled that DTS package, but I'd really like to
> understand why this server is running jobs under the non-sa account.
>

Job Names Created for Subscriptions

Hi All,
I'm new to Reporting Services and have just created my first data-driven
subscription for a report. In the SQL Enterprise Manager, the job name seems
to take the shape of a GUID. Is there a way around this so administration is
easier and these names are "human readable"?
Thanks in advance!
Kind regards - FredI'd also like to know the answer to this. The DBAs here likes to keep a
close eye on the jobs and they seem really annoyed by these GUIDs. I pointed
out that they could see it was a Reporting Services job and they could sort
on that column to put them all together but they didn't really consider that
a good solution.sql

Job is not executing in parallel

I just thought I would share this info:

I created the package to download 4 ftp files at once.
I set the MaxConcurrentExecutables for the SSIS package to 4. So in BIDS in downloads 4 files at the same time.

However, when I started the job I noticed that only 3 files were downloaded at the time (looking at temp files in download directory)

Solution:
Sure enough after digging around for awhile - in Step properties for SSIS package - there is execution tab - and "Maximum Concurrent Executables" was -1 (which for some reason defaults to 3 concurrent processes even on our dual CPU server) - so after chanign that value to 4 - tada - all 4 files in parallel

I found 2 different versions about the behavior of SSIS when the default value of MaxConcurrentExecutables property is used.

If you look at BOL (http://msdn2.microsoft.com/en-us/library/ms137749.aspx) it says :"The number of executable files that the package can run concurrently. The default value of this property is -1, which indicates that there is no limit."

But if you look at 'Integration Services: Performance Tuning Techniques' white paper (http://www.microsoft.com/technet/prodtechnol/sql/2005/ssisperf.mspx); it says "By default, this is set to -1, which translates to the number of logical machine processors plus 2. "

However, any of these 2 descriptions seems to be consistent with what you are describing. I belive the second version is closer to the true; but It would be interesting to get a confirmation of that.

Rafael Salas

Job from Local DTS Package not running

Hi,

I created a DTS to run a VB.net exe from local packages dts.
If I execute the package, it would do what I want.
I scheduled it to be a job running every minute of every day to test out the schedule.

The job status only stays at "Excuting Job Step 1"...and this hangs there forever.

I've check my SQLServerAgent is started.

Some info:
my sqlserveragent service is run under a username specifically for SQLServer I call "SQLService".
I'm using SQL Server Developer Edition.

Anyone can explain why this is happenning? I'm running into dead alleys here.Why do you want to do that using SQL . Can It not be done through Windows task Scheduler ?|||Cause it needs to be refresh almost a few minutes...or hour..depending..

Windows Task shceduler...I'm using w2k...only details the time of the day, and repeats only on "daily" basis.

So...anything I should check?|||Try going to the advanced schedule properties in windows task scheduler ... you can schedule for every hour nad minute|||Thanks, I can see the detail settings from my home pc...(XP)...
Will try that once I'm at work.

Well...if it works...anything goes...but for knowledge sake, what could have possibly cause the job to just hang? Any ideas?|||I dont think you can call an external exe from a job or xp_cmdshell ... havent found out a way to do so yet.

Job failure notification

Hello,
I created a job that will execute two dts packages at night. Both back up
different databases from the remote server to the local server, so they are
not dependent on each other. Also, if the first one fails, the job steps to
the second one. However, I would like to be notified if either/both of them
fail (and know which one failed).
Can I do this or should I have two separate jobs. If possible, I would
rather get an email saying DTS Package 1 failed versus having to look at the
each log file to determine which one failed.
--
Thanks in advance,
StevenWhy are you using DTS to do backups ?
You can have a job fire that will backup databases. You would have a job
per server you wanted to backup. You can specify the location of the backup
file using UNC. When you say backup do you actually mean data transfer ?
--
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
"Steven K" <sckeels@.lucent.com> wrote in message
news:uspA2dlRDHA.2116@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I created a job that will execute two dts packages at night. Both back up
> different databases from the remote server to the local server, so they
are
> not dependent on each other. Also, if the first one fails, the job steps
to
> the second one. However, I would like to be notified if either/both of
them
> fail (and know which one failed).
> Can I do this or should I have two separate jobs. If possible, I would
> rather get an email saying DTS Package 1 failed versus having to look at
the
> each log file to determine which one failed.
> --
> Thanks in advance,
> Steven
>|||Sorry Allan,
What I meant to write was data transfer.
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OtAVkklRDHA.3132@.tk2msftngp13.phx.gbl...
> Why are you using DTS to do backups ?
> You can have a job fire that will backup databases. You would have a job
> per server you wanted to backup. You can specify the location of the
backup
> file using UNC. When you say backup do you actually mean data transfer ?
> --
>
> 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
> "Steven K" <sckeels@.lucent.com> wrote in message
> news:uspA2dlRDHA.2116@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > I created a job that will execute two dts packages at night. Both back
up
> > different databases from the remote server to the local server, so they
> are
> > not dependent on each other. Also, if the first one fails, the job
steps
> to
> > the second one. However, I would like to be notified if either/both of
> them
> > fail (and know which one failed).
> >
> > Can I do this or should I have two separate jobs. If possible, I would
> > rather get an email saying DTS Package 1 failed versus having to look at
> the
> > each log file to determine which one failed.
> >
> > --
> > Thanks in advance,
> >
> > Steven
> >
> >
>

Job Fails when scheduled

Another user who has sa privledges created a job to run an update on a table
.
I modifed it for him. Then I shceduled it. I or he can run it manaully and i
t
works fine, but when scheduled, it bombs everytime. HELPHope this article might be of some help
http://support.microsoft.com/defaul...;283811&sd=tech
"DBA" wrote:

> Another user who has sa privledges created a job to run an update on a tab
le.
> I modifed it for him. Then I shceduled it. I or he can run it manaully and
it
> works fine, but when scheduled, it bombs everytime. HELP

job fails for sql 2005 run SSIS package

Hi, I created an SSIS package and deployed it by using the wizard that is
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails and
the only message I get is
**************************************************
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.
I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
Paul G
Software engineer.
"Paul" wrote:

> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MSDB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails and
> the only message I get is
> **************************************************
> Message
> The job failed. The Job was invoked by User domain\username. The last step
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication and
> it found the package. I am running everything on one machine as I just have
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.

job fails for sql 2005 run SSIS package

Hi, I created an SSIS package and deployed it by using the wizard that is
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails an
d
the only message I get is
****************************************
**********
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
Paul G
Software engineer.
"Paul" wrote:

> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MS
DB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails
and
> the only message I get is
> ****************************************
**********
> Message
> The job failed. The Job was invoked by User domain\username. The last st
ep
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication a
nd
> it found the package. I am running everything on one machine as I just ha
ve
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.