How to define SSIS packages complexity, which are consider as simple,medium,complex packages? Any standard definitions by Microsoft?Navin.D http://dnavin.wordpress.com

I am afraid, but no. The complexity is driven by business requirements onlyPlease vote as helpful or mark as answer, if it helps

Presumably this is for some sort of estimating process. You would have to define that by number of data sources, columns, operations, etc and expected build / test time. Usually you'd just categorise that up into day's effort and get someone who understands SSIS / ETL to lump deliverables into teh appropriate bucket.James Beresford @ www.bimonkey.com & @BI_Monkey SSIS / MSBI Consultant in Sydney, Australia SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex

Hi Navind, Thanks for the question and other partners’ replies. Gennerally speaking, we should order the business logic to create the packages, there is still need one standard for this design. There is one video that has one good description for this requirement, I would suggest see it for a reference: How to Plan the Design of an SSIS Package Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

Package complexity is very subjective. Its definition can depend upon the number of tasks/transformations/variables/components/sources/destinations etc. used in the package or the business logic embedded in the package. There could be very few tasks in the package but one script task can hold very complex business logic. Estimated or actual effort for development may not be good indicator because some simple packages may require repetitive activity that prolongs the development. Lastly, something that is simple for an experienced developer could be considered complex for a fresher.Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers. Thanks! Aalam | Blog (http://aalamrangi.wordpress.com)