Anyone know why the Execute SQL Task is only available under Control flow and not Data flow (At times it's a useful data manipuation task and I wish was available as a Data flow task as well.)
Barkingdog
Asymmetry in "Execute SQL Task"?
Hot Topic
- Cache calculated member
- SQL Server Management Studio Reports "Column Prefix" errors on fields such as [First.Name] and [Last.Name]
- How can i treate Huge DB size in sql server 2000
- Where are the sql 2005 Templates stored?
- Inscope at Matrix subtotal
- help with index: what's the difference?
- backup Maintenance wizard
- Copy table Structure including primary keys, index etc.
- How to specify config file for package within a package
- Line feed problem in HTML
SQL Server
- System Monitor logging of SQlServer counters
- sql 2005 downgrade to sql 7.0
- Report Server Windows Service
- SSIS - Several Bugs in creating a simple task
- SQL Server 2005 and "SQL Server" driver
- Absolute Beginner in SQL 2005 EE, needs help.
- range - left our join
- sys.Conversation_Endpoints
- Database.EnumObjects doesn't retrieve triggers information
- Time intelligence
Asymmetry in "Execute SQL Task"?
TitanX
It could lead to some extremely inefficient data flows.
Imagine executing a SQL statement for every record in a 1,000,000 row transformation
Or what if you decided to execute an update against the source data in your transformation
The posiibilities for abuse are staggering...
If you need to run a SQL task doing it before or after a transformation allows you to execute SQL on the entire set... Not just a single record.
Michael Vanhoutte