January 22, 2015 at 4:24 am
u mean to say that , dont delete the project in the SSIS DB catalog and just deploy the .ispac on the same folder in the SSISDB catalog ?
January 22, 2015 at 4:24 am
I do suggest, however, that you do this 'redeployment' by right-clicking on the 'Projects' node in your SSISDB catalog and selecting Deploy.
January 22, 2015 at 4:25 am
Guitar_player (1/22/2015)
u mean to say that , dont delete the project in the SSIS DB catalog and just deploy the .ispac on the same folder in the SSISDB catalog ?
Exactly. Your redeployment will write over the top of it.
January 22, 2015 at 4:27 am
that means .....ok let me check and get back to you
February 9, 2015 at 2:38 am
That helped bro !!! Thanks for the info ..
February 9, 2015 at 2:52 am
Hi Phil,
I need another help from you , currently in our project we have given as "DoNotSaveSensitive" as the Encrypt level , suppose if the case is like i dont want to show the password of the connection string how can i achieve it ?
In my current project , i have given the connection strings to the parameters and i am passing the environment variables to these parameters through job , but there the password is open .
I have tried by giving sensitive property to TRUE in the project parameters and also in the environment variables as "TRUE", but when i execute the job , it is throwing me an error like
Error: 0xC0017010 at Package: The expression will not be evaluated because it contains sensitive parameter variable "$Project::OraConnectionString". Verify that the expression is used properly and that it protects the sensitive information.
February 9, 2015 at 3:10 am
Guitar_player (2/9/2015)
Hi Phil,I need another help from you , currently in our project we have given as "DoNotSaveSensitive" as the Encrypt level , suppose if the case is like i dont want to show the password of the connection string how can i achieve it ?
In my current project , i have given the connection strings to the parameters and i am passing the environment variables to these parameters through job , but there the password is open .
I have tried by giving sensitive property to TRUE in the project parameters and also in the environment variables as "TRUE", but when i execute the job , it is throwing me an error like
Error: 0xC0017010 at Package: The expression will not be evaluated because it contains sensitive parameter variable "$Project::OraConnectionString". Verify that the expression is used properly and that it protects the sensitive information.
Don't Save Sensitive is the right package setting, in my opinion.
Passwords and other sensitive values can be passed into the package as 'sensitive' parameters from an environment.
February 9, 2015 at 3:13 am
HOW ?
February 9, 2015 at 3:34 am
nope....this was checked already
February 9, 2015 at 3:35 am
Does your package contain an expression with a sensitive parameter?
February 9, 2015 at 4:05 am
my parameter doesnt contain any expression
February 9, 2015 at 4:08 am
Guitar_player (2/9/2015)
my parameter doesnt contain any expression
But does an expression contain the parameter?
February 9, 2015 at 4:13 am
Let me explain,
We will have project connections in our connection manager , so i right click on them and clicked on "Parameterize" option
and selected the connection string and manually entered in it 'Password=xxx' and saved and when i ran it the package and project are working fine !! so i have copied the same connection string in the environment variable reference in the catalog and passed the same to the project
Now my requirement is i am going to make them sensitive by checking the 'Sensitive' property to TRUE in project params and in the catalog ,
There i am getting the error !!!
February 9, 2015 at 4:27 am
Guitar_player (2/9/2015)
Let me explain,We will have project connections in our connection manager , so i right click on them and clicked on "Parameterize" option
and selected the connection string and manually entered in it 'Password=xxx' and saved and when i ran it the package and project are working fine !! so i have copied the same connection string in the environment variable reference in the catalog and passed the same to the project
Now my requirement is i am going to make them sensitive by checking the 'Sensitive' property to TRUE in project params and in the catalog ,
There i am getting the error !!!
Did you try parametrising the individual properties of the connection string, rather than the entire thing, as suggested by the thread I mentioned earlier?
Viewing 15 posts - 16 through 30 (of 36 total)
You must be logged in to reply to this topic. Login to reply