i have 3 2008-style ssis packages think i've done pretty job upgrading 2016 tooling. i've migrated project deployment @ top level , i'm using project params - seems big improvement.
my first problem when deploy server, seems succeed, integration services explorer mode in ssms shows no packages in place expect see them. new folder there there's nothing in it. able use 7zip uncompress .ispac file in /bin folder being deployed , indeed contain .dtsx files expect see.
when deploy, deployment wizard lists .ispac file path under source section, not individual packages. that's fine i'll mention in case should see individual packages listed.
i notice there's option "convert deployment model" under visual studio project's ssis packages section - that's separate "convert package/project deployment" @ project-level. it's separate "upgrade packages" option has been done , there no remaining upgradable packages.
when run "convert deployment model" wizard , try "next" past screen packages listed "not loaded" status, error "one or more selected packages not ready" an error status on packages message the variable "$project::serverb" not found in variables collection. variable might not exist in correct scope.
@[$project::serverb] indeed variable in of packages. , in @ least 1 of xml content of package files can see listed in 1 place. in editor (the expression field of sql connection manager) use variable project parameter evaluates configured value fine.
what "convert deployment model" option anyway, separate "convert package/project deployment" option? same, , 1 on "ssis package" folder failing validate conversion (back package deployment) because there project parameters resulting package deployment mode doesn't support, hence error?
and importantly, why aren't packages getting deployed? deployment model thing red herring @ point? should seeing?
thanks!
i looking in wrong spot. in ssms, see them under database engine side of object explorer, not under integration services side. integration services had folder might have been carried on old deployments , seems no longer necessary. under database there new "integration services catalogs" folder shows projects along expected deployed packages.
i guess "convert deployment model" distraction.
Comments
Post a Comment