I had an SSIS package that was deployed to the SSIS catalog called package.dtsx. I renamed this package (In SSIS Data Tools by right clicking on the package and selecting rename) to Client1.dtsx and then deployed it to the catalog.
So at this point I had Client1.dtsx AND package.dtsx in the catalog which technically is a duplicate (just different names). So I deleted the package.dtsx by using the below code in SQL:
BEGIN TRAN
DELETE [pkg]
FROM
[SSISDB].[internal].[projects] AS [proj] WITH (NOLOCK)
INNER JOIN
[SSISDB].[internal].[packages] AS [pkg] WITH (NOLOCK) ON
[pkg].[project_id] = [proj].[project_id]
WHERE
[proj].[name] = 'Company'
AND [pkg].[name] in ('Package.dtsx')
COMMIT
At this point I only have Client1.dtsx in the catalog which is exactly what I want.
The problem I’m facing now is that every time I make a change in the package on data tools and redeploy the package to the SQL catalog it deploys Client1.dtsx but ALSO package.dtsx.
It’s almost like it’s still saving the old package somewhere.
In my windows directory, where the dtsx packages are stored, I only have Client1.dtsx and also only Client1.dtsx exists in data tools in the list of packages within my project.
my structure in data tools is like so:
Solution –> Project –> One dtsx package for each client that we have ie Client1.dtsx, Client2.dtsx etc.
So everytime I make a change to a package, I just redeploy the package itself and this works fine, unless I rename the package from data tools as mentioned above
what am I doing wrong?
5