Hi,

I'm trying to use an environment variable for SQL Server connection string (data source + initial catalog + SQL Server login)

and an environment variable for the corresponding (sensitive) password.

Sometimes (not always) I've obtained a "Login failed for user ..." error. A preceeding message says:

"Failed to acquire connection "SQL_Server_Connection". Connection may not be configured correctly or you may not have the right

permissions on this connection."

Obviously, the connection string and the password have the right value!

Have you encountered a such error for a similar case (connection string + sql server login + environment variables)?

Perhaps, the (sensitive) password is lost if passed by an environment variable. Perhaps, it is more right to write it manually for the project parameter deployed in the SSIS catalog with the solution.

For these reasons, I'd like to read replies from who has experienced with this subject.

In a such scenario, where I need to use SQL Server login and not Windows credential, perhaps using a SSIS proxy isn't the better solution.

Many thanks