Showing posts with label migrated. Show all posts
Showing posts with label migrated. Show all posts

Thursday, March 22, 2012

DTS packages fail after server migration

Hi All
My DTS packages fail after i have migrated my sql server from a NT based
network to a windows 2003 based network and unattached the old domain, I
know that the users that was once on the server as %old domain%\user will no
longer have any rights on the sql server, But how can i change the ownership
of those DTS packages to %New Domain%\New AD User.?
some input would be great.
thanksHave you checked SQLDTS.com. I believe package ownership issues are covered
on that site.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Todd" <Todd_c_wright@.hotmail.com> wrote in message
news:uVew3tSDEHA.3348@.TK2MSFTNGP11.phx.gbl...
Hi All
My DTS packages fail after i have migrated my sql server from a NT based
network to a windows 2003 based network and unattached the old domain, I
know that the users that was once on the server as %old domain%\user will no
longer have any rights on the sql server, But how can i change the ownership
of those DTS packages to %New Domain%\New AD User.?
some input would be great.
thanks|||You can change the owner using the undocumented
sp_reassign_dtspackageowner but the package ownership
probably has nothing to do with the packages failing. You
can sometimes run into issues when someone who isn't the
owner and isn't a sysadmin attempts to modify and save
packages owned by someone else but that's about it.
You can find more info on this at the site Vyas referred you
to:
Package Ownership Issues
http://www.sqldts.com/default.aspx?212
Are these scheduled packages that are failing or do they
fail when run manually as well? What are the errors?
-Sue
On Fri, 19 Mar 2004 09:56:27 +1300, "Todd"
<Todd_c_wright@.hotmail.com> wrote:

>Hi All
>My DTS packages fail after i have migrated my sql server from a NT based
>network to a windows 2003 based network and unattached the old domain, I
>know that the users that was once on the server as %old domain%\user will n
o
>longer have any rights on the sql server, But how can i change the ownershi
p
>of those DTS packages to %New Domain%\New AD User.?
> some input would be great.
> thanks
>

Sunday, February 26, 2012

DTS migration wizard, where does it put migrated version?

From SQL Server Management Studio I right click on Management/Legacy/DTS and select Migration Wizard and enter a SQL Server Source and Destination. A list of DTS packages from the source server is displayed and I select one of the DTS packages and give the destination a unique name. The wizard runs and says it's successful. I can't find the new SSIS version of the DTS package with the new name that I've given it, however. Where does it put the new migrated copy of the DTS package.

Thanks,

John

In Sql Management Studio, under the Object Explorer window in the Connect drop down choose Integration Services, and it will show you all stored packages on that instance.|||Thanks, this helps. Now I'd like to find out how to edit the migrated version. How to I get to it from BI Dev Studio?|||

All of the stored packages will usually be in ~\Program Files\Microsoft SQL Server\90\DTS\Packages

DTS migration wizard, how to edit MSDB packages?

Thanks to Sean for helping me find the migrated packages. I'd like to edit one of the connections on a bunch of packages that I migrated. I see in the Run Package there are configuration options that would allow me to mofify the connection string at that point in time, but I would like to modify the package so it has the new connection string. I was thinking I could access it in BI Dev studio, but I'm not sure how to get to it. I suppose I could migrate to a file and then edit the file prior to importing, but I'm curious if there's a way I can modify the packages that show up under Integration Services/Stored Packages/MSDB.

Thanks,

John

You'll have to export it to a file, and then edit it with BIDS. Afterwards import it back in. :)