Can''t see SSIS package saved as a maintenance plan

Question

Can''t see SSIS package saved as a maintenance plan

Mike Landa

SSC Eights!

Points: 858
More actions
November 9, 2006 at 6:18 pm

#115050

Guys,
I've created a package in Visual Studio 2005 and deployed it to SQL Server 2005 msdb. I can see it in msdb.dbo.sysdtspackages90 table, but can't see that entry as a maintenance plan. I've created another plan thru SQL Server 2005 Management Studio and can see it in both places (sysdtspackages90 table and maintenance plan folder). Any thougts ?
Mike

Viewing 5 posts - 1 through 4 (of 4 total)

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

kaddie abdul SSC Eights! Points: 866 More actions · Answer 1

I don't think that you can generate a maintenance plan that will appear in the maintenance plan folder except by using SSMS.

You can generate a package with Maintenance Plan tasks that you can subsequently deploy to your server and execute as a job, however I don't think that SSMS permits you to store that pkg in the Maintenance Plan folder.

Weird...

Mike Landa SSC Eights! Points: 858 More actions · Answer 2

Kaddie,

I'm new to SSIS and what is mechanism to deploy a package from VS 2005 to SQL Server 2005 to schedule it as a job later ? I've followed Books online approach called "How to: Save a Copy of a Package".

Thank you, Mike.

kaddie abdul SSC Eights! Points: 866 More actions · Answer 3

Hi Mike,

What you want to use is the Deployment Manifest tool to deploy your package to the server. The "How To: Deploy Packages To SQL Server" help topic in SSIS help will tell you the exact steps that you need to follow.

After you deploy your package, go to SSMS and connect to the Integrations Service for that database. If you deployed your package to the File System (and this is by far the easiest option), then go to the Stored Packages folder under Integration Services and expand the File System folder. You should be able to see the folder that you specified during the deployment. Expand that folder and you should see your package.

At this point you can right click on your package to see a couple of different options including "Run Package".

You can also go back to your Database Service in SSMS, and schedule a job that accesses the package now that it has been deployed to your DB server. Just make sure that in the Step property for the Job, you select "Sql Server Integration Services Package" in the type field, “File System” in the Package Source field, and the physical location of the package (i.e., the SQL Server 90 folder...) in the Package field. Everything else is pretty straightforward.

Hope this helps.

Mike Landa SSC Eights! Points: 858 More actions · Answer 4

Kaddie,

thank you. SSIS is not GUI intuitive as DTS is. To me the entire SQL Server 2005 environment looks very cumbersome. It doesn't look like a Microsoft product anymore...