Scheduling an MSDB SSIS package

  • Here's a good one - anyone know why this happened?

    1. Create an SSIS2005 package.

    2. Import it into MSDB under a sub - folder.

    3. Attempt to schedule the task in Agent - select Package Source SQL Server, Server = the default instance; the package is MISSING from the list, even though the folder, and the other packages in the folder, are present.

    4. Specify Server = the other (non - default) instance and the package is there, along with the other 2 which showed when the default instance was selected.

    There are 2 instances of SQL2005 on the box. I don't know when SSIS was installed - with an instance or separately. Everything has been done with a server admin and SQL sysadmin account.

    So, why do some packages appear in both servers' MSDBs and some in only one, and how does SSIS decide which MSDB it'll use?

    Thanks for your help - if you can! This is driving me slightly wibble!

  • Sorry, all - this is actually SQL2008 not 2005 but I can't see how to switch forum/delete the post so I've created a new one in 2008 General!

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply