config file contents and deployement

Hi all,

I have few config files with db passwords in them. I have to change passwords daily into that(as my system is in UAT phase now). I have deployed my packages on SQL Server.

My question is , do I need to deploy my packages daily after password updation, or it'll automatically taken care by the SQL Server ?

Thanks in Advance

syed

If you are using package configuration files, you should be able to modify just the config file, and not have to re-deploy the packages.|||

thanks for ur response John !!

Can you please tell me how internally it works so that i can have a better picture ?

thanks

|||

The topic "Package Configurations" in Books Online explains it much better than I can

Basically, configurations allow you to store settings for your package outside of the pacakge (in a file, a database, env. variables, etc.). At runtime, the package reads the configurations when it first starts up, and uses the values specified in the configuration when it is executing. You can set connection strings, variable values, task properties, and more through configuration.

config file contents and deployement

Hi all,

I have few config files with db passwords in them. I have to change passwords daily into that(as my system is in UAT phase now). I have deployed my packages on SQL Server.

My question is , do I need to deploy my packages daily after password updation, or it'll automatically taken care by the SQL Server ?

Thanks in Advance

syed

If you are using package configuration files, you should be able to modify just the config file, and not have to re-deploy the packages.|||

thanks for ur response John !!

Can you please tell me how internally it works so that i can have a better picture ?

thanks

|||

The topic "Package Configurations" in Books Online explains it much better than I can

Basically, configurations allow you to store settings for your package outside of the pacakge (in a file, a database, env. variables, etc.). At runtime, the package reads the configurations when it first starts up, and uses the values specified in the configuration when it is executing. You can set connection strings, variable values, task properties, and more through configuration.

Conditional execution of first task

I have a situation where I'd like to conditionally execute the first task in a package based on the contents of a user variable.

If user variable "Var1" is false I want to begin execution with the first task.

If "Var1" is true I want to begin execution at the second task.

My first thought of course was SequenceContainer, but the same issue would exist for the first task in a SequenceContainer.

Is there a way to do this?

Thanks!

To conditionally execute a task you would use a constraint with an expression on it, but you need two tasks (containers) to do this. The ideal answer is to use something that does nothing, but offers a start point for the constraint. A sequence container works rather well, just drop it on and collpase it (the arrow on the right-hand side of the header). You can then link that to the real task, nothing should go inside that sequence container.|||

I have created a sample solution inline with Darren's suggeston to use 'Sequence Container' for placing the precedence condition @. http://mystutter.blogspot.com/2006/03/sql-server-integration-services.html

Please let me know your comments.

Thanks,
Loonysan

|||

Thank you. Your example was perfect.

I found another solution as well. I created a Sequence Container, inside that I created another Sequence Container and my first task. I put an expression constraint between those. Then I linked the outer Sequence Container to the second task.

I appreciate the help.