Also, a Channel 9 webcast goes into technical details about setting up and using CDC, but this is what's in it for you:

• If you use CDC you can forget about writing and maintaining additional code just for compliance purpose.
• You stop worrying whether your additional database updates slow down the performance of core functions, as CDC tracks data asynchronously. (If you have doubts about performance check out this case study about Austrian sports broadcasters.)
• You don't have to prove to anyone that your compliance code does what it's supposed to, as you can point to the well-defined and published features of your database that you simply turn on.
• You can reliably access captured data in a relational format. Already there are tools that help you manage the data from CDC: http://www.codeplex.com/CDCHelper.

On the other hand, you may not need to save detailed history of all updates to your data. Perhaps you only need to know that data in certain columns changed or track the user making the changes. Then consider Change Tracking or Auditing features of SQL Server 2008.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_3.php http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_3.php Wed, 12 Nov 2008 16:39:00 -0700
Enter SQL Server 2008, assuming it's easy for you to upgrade to that latest release (and it probably is, if you are already on SQL Server 2005). Its new Change Data Capture (CDC) feature copies the data for the tables you specify. While designed to support ETL processes for efficient loading of data warehouses or marts, it can serve well in scenarios where much of the data changes must be captured and stored in separate tables. Here's a data flow diagram in data warehousing scenario:

Also, a Channel 9 webcast goes into technical details about setting up and using CDC, but this is what's in it for you:

• If you use CDC you can forget about writing and maintaining additional code just for compliance purpose.
• You stop worrying whether your additional database updates slow down the performance of core functions, as CDC tracks data asynchronously. (If you have doubts about performance check out this case study about Austrian sports broadcasters.)
• You don't have to prove to anyone that your compliance code does what it's supposed to, as you can point to the well-defined and published features of your database that you simply turn on.
• You can reliably access captured data in a relational format. Already there are tools that help you manage the data from CDC: http://www.codeplex.com/CDCHelper.

On the other hand, you may not need to save detailed history of all updates to your data. Perhaps you only need to know that data in certain columns changed or track the user making the changes. Then consider Change Tracking or Auditing features of SQL Server 2008.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_1.php http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_1.php Wed, 12 Nov 2008 16:39:00 -0700
Enter SQL Server 2008, assuming it's easy for you to upgrade to that latest release (and it probably is, if you are already on SQL Server 2005). Its new Change Data Capture (CDC) feature copies the data for the tables you specify. While designed to support ETL processes for efficient loading of data warehouses or marts, it can serve well in scenarios where much of the data changes must be captured and stored in separate tables. Here's a data flow diagram in data warehousing scenario:

Also, a Channel 9 webcast goes into technical details about setting up and using CDC, but this is what's in it for you:

• If you use CDC you can forget about writing and maintaining additional code just for compliance purpose.
• You stop worrying whether your additional database updates slow down the performance of core functions, as CDC tracks data asynchronously. (If you have doubts about performance check out this case study about Austrian sports broadcasters.)
• You don't have to prove to anyone that your compliance code does what it's supposed to, as you can point to the well-defined and published features of your database that you simply turn on.
• You can reliably access captured data in a relational format. Already there are tools that help you manage the data from CDC: http://www.codeplex.com/CDCHelper.

On the other hand, you may not need to save detailed history of all updates to your data. Perhaps you only need to know that data in certain columns changed or track the user making the changes. Then consider Change Tracking or Auditing features of SQL Server 2008.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ.php http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ.php Wed, 12 Nov 2008 16:39:00 -0700
Enter SQL Server 2008, assuming it's easy for you to upgrade to that latest release (and it probably is, if you are already on SQL Server 2005). Its new Change Data Capture (CDC) feature copies the data for the tables you specify. While designed to support ETL processes for efficient loading of data warehouses or marts, it can serve well in scenarios where much of the data changes must be captured and stored in separate tables. Here's a data flow diagram in data warehousing scenario:

Also, a Channel 9 webcast goes into technical details about setting up and using CDC, but this is what's in it for you:

• If you use CDC you can forget about writing and maintaining additional code just for compliance purpose.
• You stop worrying whether your additional database updates slow down the performance of core functions, as CDC tracks data asynchronously. (If you have doubts about performance check out this case study about Austrian sports broadcasters.)
• You don't have to prove to anyone that your compliance code does what it's supposed to, as you can point to the well-defined and published features of your database that you simply turn on.
• You can reliably access captured data in a relational format. Already there are tools that help you manage the data from CDC: http://www.codeplex.com/CDCHelper.

On the other hand, you may not need to save detailed history of all updates to your data. Perhaps you only need to know that data in certain columns changed or track the user making the changes. Then consider Change Tracking or Auditing features of SQL Server 2008.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_2.php http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_2.php Wed, 12 Nov 2008 16:39:00 -0700
Enter SQL Server 2008, assuming it's easy for you to upgrade to that latest release (and it probably is, if you are already on SQL Server 2005). Its new Change Data Capture (CDC) feature copies the data for the tables you specify. While designed to support ETL processes for efficient loading of data warehouses or marts, it can serve well in scenarios where much of the data changes must be captured and stored in separate tables. Here's a data flow diagram in data warehousing scenario:

Also, a Channel 9 webcast goes into technical details about setting up and using CDC, but this is what's in it for you:

• If you use CDC you can forget about writing and maintaining additional code just for compliance purpose.
• You stop worrying whether your additional database updates slow down the performance of core functions, as CDC tracks data asynchronously. (If you have doubts about performance check out this case study about Austrian sports broadcasters.)
• You don't have to prove to anyone that your compliance code does what it's supposed to, as you can point to the well-defined and published features of your database that you simply turn on.
• You can reliably access captured data in a relational format. Already there are tools that help you manage the data from CDC: http://www.codeplex.com/CDCHelper.

On the other hand, you may not need to save detailed history of all updates to your data. Perhaps you only need to know that data in certain columns changed or track the user making the changes. Then consider Change Tracking or Auditing features of SQL Server 2008.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/hand_off_your_c.php http://www.beyeblogs.com/rda_corp/archive/2008/11/hand_off_your_c.php Wed, 12 Nov 2008 16:39:00 -0700
Enter SQL Server 2008, assuming it's easy for you to upgrade to that latest release (and it probably is, if you are already on SQL Server 2005). Its new Change Data Capture (CDC) feature copies the data for the tables you specify. While designed to support ETL processes for efficient loading of data warehouses or marts, it can serve well in scenarios where much of the data changes must be captured and stored in separate tables. Here's a data flow diagram in data warehousing scenario:

Also, a Channel 9 webcast goes into technical details about setting up and using CDC, but this is what's in it for you:

• If you use CDC you can forget about writing and maintaining additional code just for compliance purpose.
• You stop worrying whether your additional database updates slow down the performance of core functions, as CDC tracks data asynchronously. (If you have doubts about performance check out this case study about Austrian sports broadcasters.)
• You don't have to prove to anyone that your compliance code does what it's supposed to, as you can point to the well-defined and published features of your database that you simply turn on.
• You can reliably access captured data in a relational format. Already there are tools that help you manage the data from CDC: http://www.codeplex.com/CDCHelper.

On the other hand, you may not need to save detailed history of all updates to your data. Perhaps you only need to know that data in certain columns changed or track the user making the changes. Then consider Change Tracking or Auditing features of SQL Server 2008.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_4.php http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_are_writ_4.php Wed, 12 Nov 2008 16:39:00 -0700
Enter SQL Server 2008, assuming it's easy for you to upgrade to that latest release (and it probably is, if you are already on SQL Server 2005). Its new Change Data Capture (CDC) feature copies the data for the tables you specify. While designed to support ETL processes for efficient loading of data warehouses or marts, it can serve well in scenarios where much of the data changes must be captured and stored in separate tables. Here's a data flow diagram in data warehousing scenario:

Also, a Channel 9 webcast goes into technical details about setting up and using CDC, but this is what's in it for you:

• If you use CDC you can forget about writing and maintaining additional code just for compliance purpose.
• You stop worrying whether your additional database updates slow down the performance of core functions, as CDC tracks data asynchronously. (If you have doubts about performance check out this case study about Austrian sports broadcasters.)
• You don't have to prove to anyone that your compliance code does what it's supposed to, as you can point to the well-defined and published features of your database that you simply turn on.
• You can reliably access captured data in a relational format. Already there are tools that help you manage the data from CDC: http://www.codeplex.com/CDCHelper.

On the other hand, you may not need to save detailed history of all updates to your data. Perhaps you only need to know that data in certain columns changed or track the user making the changes. Then consider Change Tracking or Auditing features of SQL Server 2008.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/hand_off_your_c_1.php http://www.beyeblogs.com/rda_corp/archive/2008/11/hand_off_your_c_1.php Wed, 12 Nov 2008 16:39:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_456.php http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_456.php Tue, 11 Nov 2008 08:22:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_408.php http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_408.php Tue, 11 Nov 2008 08:22:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_384.php http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_384.php Tue, 11 Nov 2008 08:22:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_432.php http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_432.php Tue, 11 Nov 2008 08:22:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/ssis_package_la_1.php http://www.beyeblogs.com/rda_corp/archive/2008/11/ssis_package_la_1.php Tue, 11 Nov 2008 08:22:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_480.php http://www.beyeblogs.com/rda_corp/archive/2008/11/quot_480.php Tue, 11 Nov 2008 08:22:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_produce.php http://www.beyeblogs.com/rda_corp/archive/2008/11/if_you_produce.php Tue, 11 Nov 2008 08:22:00 -0700 If you produce SSIS packages for a customer, even if that customer is the company you work for, then this tip is for you.

When you create a new SSIS package and start adding items to the design surface you can quickly create a mess if you're not careful.#160; Even if you are careful it is still quite difficult to precisely place the items so that the connecting lines line up.

For example, I quickly created a package which performs some common tasks:

As you can see, the various items are positioned on the design surface in a haphazard way.#160; You can spend time dragging the items around until you get a layout that looks better, or you can use the power of the Layout toolbar to assist you.

By default, the Layout toolbar is not displayed in BIDS.#160; To display it, right-click on an empty part of the toolbar and click on Layout (or you can click on Tools | Customize... and click the check box next to Layout):

#160; You should see the Layout toolbar displayed:

To fix the layout of my package, I first selected all of the items.#160; You do this either by clicking on the design surface and dragging the selection box around all of the items or by shift-clicking on each of the items until they are all selected.#160; Look closely at each of the items--one item will have white grab handles and the rest will have black grab handles.#160; The one with the white handles acts as the anchor for the items in the Layout tool bar that act on multiple items.#160; For example, if you click on the Align Lefts button, the left sides of each item will be set to the left position of the anchored item.

I used a combination of Align Lefts, Increase Vertical Spacing, and Make Vertical Spacing Equal to align my items in a vertical column:

It took my just a handful of clicks and about 20 seconds to perfectly align the items for a professional look.

If you have auto-sized any of your shapes, you are still in luck.#160; Instead of Align Lefts you can choose Align Centers to keep the arrows straight.

I'm sure that you have your favorite way to lay out your items in your packages, such as a cascading look where the arrows go down, over, and then down again.#160; While that isn't directly supported by the layout toolbar you can still make use of the toolbar to Make Vertical Space Equal after moving your items where you want them.

Leave a comment if you have additional tips for using the Layout toolbar with SSIS packages.

Farewell.

]]> http://www.beyeblogs.com/rda_corp/archive/2008/11/ssis_package_la_2.php http://www.beyeblogs.com/rda_corp/archive/2008/11/ssis_package_la_2.php Tue, 11 Nov 2008 08:22:00 -0700