Solved

xp_start_job

Posted on 2009-07-14
3
315 Views
Last Modified: 2012-05-07
We are running SQL Server 2008 64 Bit.  Ultimately we want to execute an SSIS job from a stroed procedure.  The SSIS job is a simple job that imports data from MS Access table.  No parameters need to be passed to the job.  It simply needs to be executed from a Stored Procedure.

We have integration services installed on the same server.

We crated the job called GLExport.  The job is saved on the server.  It is located int he MSDB.  The package can be run with out issue from Integration Services.  

This is the command we are trying to run from a query window:
exec msdb.dbo.sp_start_job @job_name='GLExport'

We get this error message:
Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers, Line 67
The specified @job_name ('GLExport') does not exist.

The job does exist within integration services.  However if I run select * from sysjobs my job is not there?  

Can someone please clarify how tu use the sp_start_job and pass in the proper SSIS job and or location?

Thank you
0
Comment
Question by:renoduke
  • 2
3 Comments
 
LVL 17

Accepted Solution

by:
pssandhu earned 500 total points
ID: 24849641
<<We crated the job called GLExport.  The job is saved on the server.  It is located int he MSDB>>
When a new job is created, you should be able to see it under SQL Server Agent>Jobs in SQL Server Managment Studio. Since you do not see any entry for the the Job in sysjobs table I would say the Job has not been created.
Please refer to links below on how to schedule an SSIS package in SQL Server Agent Jobs:
http://msdn.microsoft.com/en-us/library/ms139805(SQL.90).aspx
 Hope this helps.
P.
0
 
LVL 1

Author Closing Comment

by:renoduke
ID: 31603283
Thank you!  My confusion has to do with a job and SSIS package.  I did not create the job as you suggested.  For others the SSIS package is the first step.  The final step is createing the job.

Works great.
Thanks again.
0
 
LVL 17

Expert Comment

by:pssandhu
ID: 24850010
No problem!
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Naughty Me. While I was changing the database name from DB1 to DB_PROD1 (yep it's not real database name ^v^), I changed the database name and notified my application fellows that I did it. They turn on the application, and everything is working. A …
In this article I will describe the Detach & Attach method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question