January 24, 2008 at 9:27 am
I've positioned my tasks and control flow lines so that the lines don't cross and in a way that I consider logical and neat. If I come back to the package some time later, even though the tasks are all in the same place I left them, all of the control flow lines have been re-positioned and are all over the place.
Is it possible to save package layout?
Thanks,
January 28, 2008 at 3:25 am
January 28, 2008 at 10:20 am
I've never had a problem with my layouts not saving. However, in the past with DTS there were cases where your layout wouldn't be saved. How are you saving your packages?
And there's no way that I've seen to 'save layout'.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARant
January 28, 2008 at 3:01 pm
I'm just saving the packages normally through the studio designer, which saves the .dtsx file.
Maybe there's something wrong/weird about my installation. I'll see if I can find another machine to test this on.
January 28, 2008 at 3:25 pm
I haven't tested it with SSIS, but with DTS it didn't preserve your formatting when you saved it as a file. So I'm not surprised that you're having the same issue now. Test it by saving it to SQL once to see if it saves your formatting. I think you'll find it does.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARant
January 29, 2008 at 1:42 am
Perhaps it's the Tools Options settings in BIDS (aka Visual Studio 2005) that make it re-draw?
January 29, 2008 at 2:09 am
P Jones (1/29/2008)
Perhaps it's the Tools Options settings in BIDS (aka Visual Studio 2005) that make it re-draw?
That's what I thought it might be but I've been through most of the options under Tools Options and I can't find anything obvious.
crever (1/28/2008)
Test it by saving it to SQL once to see if it saves your formatting. I think you'll find it does.
I'm not sure I understand what you mean by saving it to SQL? I've imported the .dtsx package into SQL. But when I edit it in BIDS I'm always opening up the .dtsx file, rather than what I imported into SQL.
This is now getting really frustrating, particularly because it seems that other people aren't experiencing this problem :crying:.
January 29, 2008 at 6:35 am
Sounds like you're seriously missing the plot here! BIDS is designed to work on dtsx and you create in BIDS, deploy to either package store or SQL msdb. If you've somehow managed to get something different from your dtsx into sql then you need to get it back to a dtsx before you can edit in BIDS. Never tried that reverse engineering so don't know how.
January 29, 2008 at 7:23 am
P Jones (1/29/2008)
Sounds like you're seriously missing the plot here! BIDS is designed to work on dtsx and you create in BIDS, deploy to either package store or SQL msdb. If you've somehow managed to get something different from your dtsx into sql then you need to get it back to a dtsx before you can edit in BIDS. Never tried that reverse engineering so don't know how.
Sorry for the confusion. When talking about saving to SQL I was referring to crever's previous post, which suggested I save to SQL but as I see it this is a problem to do with editing packages, which as you pointed out, happens within BIDS.
Just to be clear. The package works fine. It's just that, whenever I edit the package in BIDS, the control flow lines are all over the place rather than where I placed them when I last saved the package. I know, it's not a major problem in the grand scheme of things - it's just frustrating.
January 30, 2008 at 8:02 am
It's a "feature" of bids. Worst is tasks inside containers. Most times, the green lines totally vanish. You have to "nudge" a task to get the lines back.
Also. when you open it, you tasks are totally off screen.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
January 30, 2008 at 9:43 am
I've had a similar problem, but typically the effect is my whole project shifts one way or the other, but the relationships between the objects are still the same. If you haven't done so already, try applying any Visual Studio.NET 2005 Service Packs/hotfixes in addition to the 2k5 SP2. My projects seemed to become a lot more stable after that.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply