Wrox Programmer Forums
|
SQL Server 2005 General discussion of SQL Server *2005* version only.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2005 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old April 26th, 2006, 09:43 AM
Authorized User
 
Join Date: Mar 2006
Posts: 16
Thanks: 0
Thanked 0 Times in 0 Posts
Default SSIS Packages to Jobs

I needed to create a job that would export a table from one database into a database on another server. I right clicked on my table name and selected all tasks then export data, and executed and saved the package, now I can not find the package and did not find the option to schedule when it was to execute.

Where can I find the package that I saved in Server Manager and set it up as a job so it can be scheduled?

Thanks.

 
Old April 27th, 2006, 08:34 AM
Authorized User
 
Join Date: Mar 2006
Posts: 16
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I figured it out. I didn't realize that you can't see where they are stored and have to create a new job then select Integration Services.

Now my problem is that when I manually do the steps it runs successfully but when trying to schedule the package to execute it fails with the following error message:
Executed as user: SQL01\SYSTEM. The package execution failed. The step failed.


 
Old May 8th, 2006, 12:24 PM
Registered User
 
Join Date: May 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Did you figure out what is causing this error ?

I'm getting the same failure running a package as a job



 
Old May 9th, 2006, 02:39 PM
Authorized User
 
Join Date: Mar 2006
Posts: 16
Thanks: 0
Thanked 0 Times in 0 Posts
Default

No, I never solved it. I'm wondering if it has to do with one of the servers is using SQL Server 2000 and the other is 2005. It could also have something to do with permissions not being correctly set. I've just been manually running the import/export as the priority has decreased.






Similar Threads
Thread Thread Starter Forum Replies Last Post
Controlling Print Jobs nep23 C++ Programming 1 February 5th, 2007 08:32 AM
Allow developer to shedule jobs but not as SA tuffnet SQL Server 2005 2 December 14th, 2006 05:04 PM
Controlling execution of jobs booksnore2 BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7 0 October 12th, 2004 02:42 PM
DB cron jobs ss2003 PHP Databases 1 September 14th, 2004 03:56 PM
DTS Scheduled Jobs Errors Walden SQL Server DTS 10 March 16th, 2004 10:32 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.