HI my ssis pkg contains one exec sql task I want to change the exec sql task name dynamically Is it possible I found name property in exec sql task,is this propery for that purpose? help me plz.Naresh

You can put an expression on the name property, so I would guess it's possible.MCTS, MCITP - Please mark posts as answered where appropriate.

yes you can do it with package configuration. http://msdn.microsoft.com/en-us/library/ms141682.aspx package configuration provide ability to set properties of package, tasks and connection managers dynamically at runtime.http://www.rad.pasfu.com

Beats me to understand why would you want to name a component dynamically. In-case you still want to go that way then, Select your "Execute SQL" task --> In the property windows select "Expression" --> Under Property select "Name" and under Expression specify name of the variable which has the desired component name. This variable can be loaded with the desired component name using package configurations.http://btsbee.wordpress.com/

Beats me to understand why would you want to name a component dynamically. We're actually trialling this on my current project and it surprises me to say it (given it wasn't my idea) it actually works quite well. We use an expression on a task name to represent the operation it is actually doing (eg. if its calling a sproc the name of the task might be set to "SQL Exec sprocname"). We also set the SQLStatement property dynamically using similar logic so we know that the name of the task represents the work that is being done. Why do we do it? Its to try and maintain some consistency. We try and deal with all of our incoming files using the same pattern and building the SQLStatement property dynamically enables us to do that - when we have to deal with a new incoming file we simply copy/paste an existing package, change the value of a few variables, and all the task names and Execute SQL Task SQLStatement properties change accordingly. I know it sounds bizarre and initially I was dead set against it - but I've kind of been brought around to it. We refer to this approach as "a poor man's BIML" :) ObjectStorageHelper<T> A WinRT utility for Windows 8 | http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me

it does make sense to have these scripts to auto name the components. Though would be best suited for a sizeable, large team BI project where there are repeated data flow patterns; much like a framework. Yep, and that's exactly why we do it - to promote consistent patterns. Ideally we'd be using BIML but both ourselves and the client (more so the client) weren't ready to make that jump yet.ObjectStorageHelper<T> A WinRT utility for Windows 8 | http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me

it does make sense to have these scripts to auto name the components. Though would be best suited for a sizeable, large team BI project where there are repeated data flow patterns; much like a framework. Yep, and that's exactly why we do it - to promote consistent patterns. Ideally we'd be using BIML but both ourselves and the client (more so the client) weren't ready to make that jump yet.ObjectStorageHelper<T> A WinRT utility for Windows 8 | http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me

Seeing components named as "Get me", "Flats" weird etc; it does make sense to have these scripts to auto name the components. Though would be best suited for a sizeable, large team BI project where there are repeated data flow patterns; much like a framework. http://btsbee.wordpress.com/

it does make sense to have these scripts to auto name the components. Though would be best suited for a sizeable, large team BI project where there are repeated data flow patterns; much like a framework. Yep, and that's exactly why we do it - to promote consistent patterns. Ideally we'd be using BIML but both ourselves and the client (more so the client) weren't ready to make that jump yet.ObjectStorageHelper<T> A WinRT utility for Windows 8 | http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me