I have a project that uses the SSIS catalog with project-level connection managers. The connection managers' connection strings are overridden at the server using a project parameters file, to enable easily repointing the whole project to different data sources by setting different connection strings.
Here's the issue:
- It works. No real connection problems or failures.
-
It bloats the log
tables horribly in the catalog because upon each package execution I
get:120 30 Error: The connection string format is not valid. It must
consist of one or more components of the form X=Y, separated by semicolons.
This error occurs when a connection string with zero components is set on
database connection manager.
For every connection manager, in every package. I think this has to be a false error that gets triggered when the connection string is overridden with the (correct) values in the param file.
Is there something wrong here? Some way to suppress those messages?
Best Answer
If you use the Excel connection manager for example, you should set the
ExcelFilePathproperty as an Expression instead of theConnectionString!