November 6, 2017 at 8:54 am
I have a SQL Server host running 10 named SQL Instances.
Each instance has a Daily Maintenance Plan. On each instance, I can see the plan under Management\Maintenance Plans. In the scheduled Job, I can see the package source is set to SQL Server, and the package location is Maintenance Plans\PlanName. The plans are not on the file system.
Now, I want to export the plans. So I connect to the host Integrations Services, expand Stored Package, and I only see 2 of my 10 instances listed as InstanceName_MaintenancePlan.
So where are my other 8 plans, how do I see them, and how do I export them?
November 6, 2017 at 5:47 pm
planetmatt - Monday, November 6, 2017 8:54 AMI have a SQL Server host running 10 named SQL Instances.Each instance has a Daily Maintenance Plan. On each instance, I can see the plan under Management\Maintenance Plans. In the scheduled Job, I can see the package source is set to SQL Server, and the package location is Maintenance Plans\PlanName. The plans are not on the file system.
Now, I want to export the plans. So I connect to the host Integrations Services, expand Stored Package, and I only see 2 of my 10 instances listed as InstanceName_MaintenancePlan.
So where are my other 8 plans, how do I see them, and how do I export them?
Integration Services is not aware of the other instances - it's just using whatever server or instance is in the config file. You can add additional instances. MS does explain it in the docs:
Configuring the Integration Services Service (SSIS Service)
To manage packages that are stored in a named or remote instance of the Database Engine, or in multiple instances of the Database Engine, you have to modify the configuration file for the service.
And then they don't give you any examples. So helpful, no idea why they did that. Check this link for an example:
How to Manage SSIS Packages Stored in Multiple SQL Server Database Instances
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply