May 14, 2020 at 12:22 pm
I know that it would be a ton easier to be able to deploy SSIS packages to a sql server & run them from an agent job, which would be my preferred method, but my work uses other tools as the "official" ETL Tools- namely informatica & alteryx. My department is only allowed to develop stuff in Alteryx, which has serious performance issues & also does not like to allow sequential execution. As a result, I developed some SSIS packages for an ETL job, which work well enough when executed from visual studio. However, I would like to avoid having to manually run these packages each day. The packages will eventually get converted to informatica by another department once the testing & validation of the data / reports that the packages support is complete , but in the meantime, I am stuck updating it manually every morning. I tried to get the package to run with DTexec, but I am getting an error about "Retrieving the COM class factory for component with CLSID {8957A18C-F62B-4A46-83FC-E8792FFD06DC} failed due to the following error: 8007007e The specified module could not be found. it appears to be related to the 64/ 32 bit problem, and the only copies of Dtexec on my machine all appear to be 32 bit. Is there a way I can make it possible to run my packages on a schedule from the command line until the package gets ported over? One thing I found while researching the error was to run RegSvr32 SQLTaskConnections.dll, but if I try that I get an error about it possibly being incompatible with my version of windows.
May 14, 2020 at 12:51 pm
unless you license your PC with a valid SQL Server Standard/Enterprise you can't do it for production purposes.
If you are not using those daily loads for production then you can install SQL Server Developer Edition, making sure you install the Integration Services part. That will allow the command line DTEXEC
May 14, 2020 at 2:34 pm
That is kind of what I thought. The packages are not for production, they are for development, so I guess that is one possible path. I just was hoping there was a way to avoid having to have a full sql server install on my workstation.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply