My system is currently on the package deployment model with deployment to the file system for our SSIS jobs, and we are looking to transition to a project deployment SSIS DB model. We have many packages that are all separate from each other (and differ in their variables/parameters), and each has at least one .dtsConfig file associated with it. (If they have multiple, the config files all have the same variables, but different values.)
They are not associated with projects/solutions at all. In the interest of reducing manual intervention as much as possible, I would like to be able to take a .dtsx and a .dtsConfig to create project files (.ispac and project.params) for each package, so that these can be automatically deployed to the Integration Services Catalog (using the procedure SSISDB.catalog.deploy_project). Currently I would have to use Visual Studio to create a new project, import the package, select the config, and convert to project deployment, all manually, so I'm hoping there is a way to automate this step.
I've opened an .ispac file and found it contains the package, project.params, and a project manifest, but I'm not sure which of those are completely necessary, and if there is a way to programmatically create either project.params or the manifest.
question from:
https://stackoverflow.com/questions/65830707/creating-an-ssis-ispac-from-a-dtsx-and-a-dtsconfig 与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
