What is the best way to deploy an SSIS project that has project parameters associated with connections or variable paths between environments? [closed]
Closed 8 mins ago.
¿Cuál es la mejor manera de desplegar un proyecto SSIS que tiene parámetros proyecto asociados a conexiones o rutas variables entre entornos? [closed]
Closed 55 secs ago.
I can’t create SSISDB catalog in SSMS even though SSIS is installed
Whenever i try to create the SSISDB catalog in SSMS using the company’s server (it uses docker) it doesn’t want to be created even though I installed integration services and it’s running in services, the weird thing is that when i try to do this in localhost, everything works fine for me, the problem is when connecting to the real server and trying to create the SSISDB, any help ?
SSIS Catalog connection not working in SQL Studio 20.* for New Job Step
Since version 20.* it is not possible to reference a package in an (local or remote) SSIS catalog when creating a job step in Microsoft SQL Server Management Studio without proper certificates. In this case the server is local but there does not seem to be a way to connect to “localhost” and avoid this problem (I tried ., , localhost, 127.0.0.1 …). In Microsoft SQL Server Management Studio 19.* this works without error and jobs can be created (and later on seen and run from Microsoft SQL Server Management Studio 20.*).