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
Who is Participating?
pssandhuConnect With a Mentor Commented:
<<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:
 Hope this helps.
renodukeAuthor Commented:
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.
No problem!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.