Location of precedence contraints not saved with SSIS packages, and no auto arrange
When designing SSIS package control flows, one can move the precedence contrains
around to create an easy to view layout, where the precedence constraints do NOT
overlap tasks (which looks confusing.)
This arrangement of precedence constraints is however not saved with the package -
after saving & reopening the package all precedence constraints goes back to a default
position, usually overlapping tasks.
Since the default layout is so bad (the overlaps), and there is no "auto arrange" that
does a better job, this is to me a bug.
Upvotes: 5<=-=Sep 23 2005 4:28PM=-=>
Good comment. We’ll look at this in next version<=-=Dec 7 2005 2:20PM=-=>
We could not repro this problem with RTM release of SQL Server 2005. If you can repro this, could you please provide more details and possibly attach the package that causes this behavior?<=-=Feb 15 2006 1:40PM=-=>
Not Able to Repro on RTM or SP1
The layout always remeber the position of the precedence constraints
I believe this has to do with 1 a diagram that does not fit on the page (therefore has up/down and left/right scrollbars), 3 little margin space around the edges of the diagrams, and 3 tasks that are placed fairly close together. If tasks have sufficient space between them, then it does not act up this way.<=-=Mar 29 2010 2:53PM=-=>
Here are my steps:
� Created 25 Data Flow Tasks
� Created 3 tiers of Data Flows Tasks
a. Primary Key Data
b. Foreign Key Data
c. Secondary Data
� So by this you can see I have a highly complex DB with PK and FKs.
� So at the top is going to be one table
� Add Precedence Constraint to Foreign Key Tables to pump data after PK data is established.
� Multiple FKs are selected
a. 10 Precedence Constraints assigned (10 lines)
� Each Table that is waiting for the PK table to finish will start after PK is populated.
� Each foreign key table has a primary key and foreign key reference, so they must populate before the secondary data is allowed to be inserted.
� 2 tables per FK table
a. 20 total
� 2 Precedence Constraints per FK table
� Layout is all housed up�.Lines going everywhere.
� NO hierarchical structure. No organization at all
� Format>Auto Layout>Diagram
a. Does nothing but make it worse
b. No orginzation
c. No Structure
d. Precedent constraints cross one another