Single vs Multiple Data Flows

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Data Warehousing » Integration Services » Single vs Multiple Data Flows

Single vs Multiple Data Flows

Rate Topic

Display Mode

Topic Options

Author

Message

Jason Whitney

Posted Monday, November 05, 2012 2:56 PM

SSC Rookie

Group: General Forum Members
Last Login: Friday, May 17, 2013 12:50 AM
Points: 35, Visits: 507

I have used SSIS a bit in the past (2005), but I am embarking on a new BI project and want to know the best practice for using a single vs multiple data flows. My scenario is, I have 16 databases that are 'almost' identical. Rules needed to clean and transform the data will be 90% the same, but each database will have a few outliers that will require special steps just for that db's data.

Should I:
1. Create a single data flow with 16 data sources that each have a couple db specific steps before hitting a union all clause and running the other 90% validation at once? This helps keep logic implemented in only one place even if it is more complicated to handle all the different use cases.

2. Create 16 data flows, one for each database, and duplicate all the logic in each data flow to appropriately handle the db specific issues? Each data flow is smaller, but duplicate logic is spread across the package.

Post #1381276

Koen Verbeeck

Posted Tuesday, November 06, 2012 12:11 AM

SSCrazy Eights

Group: General Forum Members
Last Login: Yesterday @ 6:51 AM
Points: 9,373, Visits: 6,470

Normally I would go for option 1, as it minimizes code duplication.
Although 16 sources are lot, which can give issues if there's memory pressure:

http://www.mattmasson.com/index.php/2012/01/too-many-sources-in-a-data-flow/

And maintaining a UNION ALL with 16 inputs is also a nightmare Smile

But so is maintaining 16 different dataflows.

I would try to go for option 1, and test out if so many sources don't give issues on your system.

How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence

Post #1381406

Jason Whitney

Posted Tuesday, November 06, 2012 5:38 PM

SSC Rookie

Group: General Forum Members
Last Login: Friday, May 17, 2013 12:50 AM
Points: 35, Visits: 507

Thanks for the advice. I will try option 1 and let you know how it goes.

Post #1381757

P Jones

Posted Wednesday, November 07, 2012 5:45 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, May 20, 2013 7:35 AM
Points: 515, Visits: 1,016

How about a for (or rather for each datasource) loop that processes one datasource at a time and has some logic inside the loop for the differences? I often use scripts to set the value of variables which can be tested as part of the constraint condition and used in connections in expressions.

Post #1381924

« Prev Topic | Next Topic »

Permissions