Recently I was trying to send a file via Email in SSIS.
For the connection to the file I was using a variable as the file name changes everyday.
This was causing an issue because it validates the whole package before the file gets generated and the package would fail.
The simplest solution was to delay the validation on the Send Mail Task. You can do this in the properties by setting Delay Validation to True.
Hope this helps you!
A while ago I was having some issues with SSIS and moving files. There was a hidden file called thumbs.db
When SSIS was running the move file task it would fail because it can’t place duplicate files in the same location. The thumbs.db file was the problem. Even though it was hidden as a windows file, SSIS still saw it and wanted to move it.
This is where limiting SSIS to a specific file type saves you from this problem.
To do this you filter on the Foreach Loop Container. You select the container and then you click on Properties.
In the Properties right at the top you shall see FileSpec. There you can set it to the file type you would like to filter/limit for.
And that’s how you limit SSIS to a specific file type!
Recently been working with getting multiple SQL Instances on one machine to work. When I uninstalled an old one it affected the latest one. Then all of a sudden my ETL jobs failed. It did not make sense at all seeing as I removed a different instance.
Got the following error when trying to run my ETL jobs or when trying to deploy the jobs:
“the path for isserverexec.exe cannot be found”
Looking for solutions online, they recommend going into the registry. Which didn’t work for me.
I ended up using the install file and running it to add features to an existing connection. And there is was Integration services was not installed for the instance that I was getting the error with.
Installed SSIS on the current instance that needed it and all worked perfectly after that and the jobs ran as perusal.
Hope this helps someone else in the future.
Before you can deploy a SSIS project you need to set up SSIS in SQL Server Management Studio. When installing SQL you will select to install SSIS, however, it does not setup the SSISSDB or configure any settings for SSIS.
Here are the steps for setting up SSIS in SQL Server Management Studio.
Right-click on Integrations Services Catalogs and select Create Catalog.
Check the box next to Enable CLR Integration and set a password for your SSISDB and click Ok.
You will then see you SSISDB listed under Databases and under Integration Services Catalogs.
Now you will be able to deploy your SSIS project to your server where you have set up SSIS.
The next post will be on deploying an SSIS project.