Hello sebnunes (AT) hotmail (DOT) com,
If I read the mail correctly you want to operate on a set of data and perform
n operations that make up a business rule. You then want to take that data
and put it into another data flow task which will perform another business
rule(s).
Is that right?
OK so there are as I can see a good number of ways you can implement this.
Here are a couple.
1. Place all your business rules in the 1 data flow task. This isn't as
bad as it might seem if you do not have that many rules that are that complex.
2. Use ExecuteSQL Tasks in the Control Flow and chain them together with
Constraints. This presupposes you have a staging area for the data
3a Use Data Flow tasks for the business processes. Again this presupposes
you have a staging area for the data
3b Use Data Flow tasks but use Raw Files as your intermediate store for
the data between business processes.
Whilst the use of a staging area and sending data to disk is minimised in
SSIS I still think there is a place for it in an ETL solutions without making
it an ELT solution
There are other ways of doing what you want here as well.
Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com
Quote:
Hi All,
I'm pretty new to SQL Server 2005 and I'm wondering how to organize my
business rules efficiently.
I'm willing to create a Package with several Data Flow Task in my
Control Flow, each Business Rule will be encapsulated in a Data Flow
task. I guess this is possible in SSIS but I can't find how my data
can be send from one data flow to another one. I definitly don't want
my dataset to be parsed completly for each business rule.
Does anyone have an idea how to implement this in SSIS?
Kind regards,
Sébastien. |