Migration from 2005 to 2000 and confused

#1

Hey. I've successfully migrated all the packages from server\instance1 to
server1\instance1. I read in one of the articles I've to change
MsDTSSrvr.ini.xml file to see the migrated packages in SSMS. I did it and now
i see the packages.
But how would I edit the package I've migrated from server\instance1?
what would I do if I had packages on server\instance2 which needed to be
migrated to server1\instance2?

Please give me more information or point me to a source. Thank you.

#2

Hello tpp,

If you want to edit them then you could open them up in BIDs (Open Existing
Package)

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Quote:

Hey. I've successfully migrated all the packages from server\instance1
to server1\instance1. I read in one of the articles I've to change
MsDTSSrvr.ini.xml file to see the migrated packages in SSMS. I did it
and now i see the packages. But how would I edit the package I've
migrated from server\instance1? what would I do if I had packages on
server\instance2 which needed to be migrated to server1\instance2?

Please give me more information or point me to a source. Thank you.

#3

I am in BID's and I go to file-->open. I dont see an option to open an
existing package. I see a file and a solution but i know tht's not it... Am I
missing somethng somewhere?? I also have the 2000 DTS Designer installed.
What am i missing? Also, when I migrated them, everything was a success. Do I
need to do anything or all of them will work fine in 2005? Thanks for the
early reply, Allan.

#4

Hello tpp,

Are you trying to open an existing 2K package or a SSIS package

If you have the Feature pack download for 2000 then you can edit 2K packages
by going to

Management | Legacy | Data Transformation Services.

If you click on that folder then you will get what you want

To edit 2K5 packages you can actually go ahead and get the file the way you
see it now. This will allow you to edit the package but that is about it.
You won't be able to run it in debug mode.

I would probably create an SSIS project and then drag the file onto the SSI
SPackage folder in the solution explorer. You can also right click on this
folder and choose to add a copy of an existing package.

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Quote:

I am in BID's and I go to file-->open. I dont see an option to open an
existing package. I see a file and a solution but i know tht's not
it... Am I missing somethng somewhere?? I also have the 2000 DTS
Designer installed. What am i missing? Also, when I migrated them,
everything was a success. Do I need to do anything or all of them will
work fine in 2005? Thanks for the early reply, Allan.

#5

Allright I'll give u a complete process of what i did. I have a server with a
named instance on 2000(Server\instance1). I've a server with SQL 2005 with a
named instance(server1\instance1). 2000 instance has the DTS packages. I
right clicked Management | Legacy | Data Transformation Services and clicked
on Migrate wizard and migrated all my DTS packages to server1\instance1.
Then, I had to change the file 'MsDTSSrvr.ini.xml' and added the instance
name in the file. I see the packages in sysDTSpackages90 table. I dont see
them under 'Management | Legacy | Data Transformation Services' But once I
changed the file and went to the Stored PAckages part of IS, I see the DTS
packages. but I dont have the option to edit them. Alos, I dont see the
option from BID. I dont have the complete feature pack but i do have
'Microsoft SQL Server 2000 DTS Designer Components' installed. Please tell me
what i'm doing wrong. Thank you, Alan.

#6

You migrated the packages so they will not be in the legacy section because
they are now SSIS packages. You should have Imported them if you wanted
them to remain as 2K packages.

In SSMS you cannot edit SSIS packages. It is a management tool. BIDs is
where we do the design. For that follow my previous instructions about
Importing a copy of an existing package.

--

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

"tpp" <tpp (AT) discussions (DOT) microsoft.com> wrote

Quote:

Allright I'll give u a complete process of what i did. I have a server
with a
named instance on 2000(Server\instance1). I've a server with SQL 2005 with
a
named instance(server1\instance1). 2000 instance has the DTS packages. I
right clicked Management | Legacy | Data Transformation Services and
clicked
on Migrate wizard and migrated all my DTS packages to server1\instance1.
Then, I had to change the file 'MsDTSSrvr.ini.xml' and added the instance
name in the file. I see the packages in sysDTSpackages90 table. I dont see
them under 'Management | Legacy | Data Transformation Services' But once
I
changed the file and went to the Stored PAckages part of IS, I see the DTS
packages. but I dont have the option to edit them. Alos, I dont see the
option from BID. I dont have the complete feature pack but i do have
'Microsoft SQL Server 2000 DTS Designer Components' installed. Please tell
me
what i'm doing wrong. Thank you, Alan.

#7

Ok, so now I understand that I've to open the packages from SSIS to edit the
package. When I open BID's do i create a new package and then import it in
that? Also, once I edit the package in SSIS, is it possible to see it in the
msdb folder for SSIS. Also, which one is better? To save it in msdb or file
system now?

#8

No you do not CREATE a new package you add a copy of an existing package by
right clicking on the SSIS Packages folder in Solution Explorer

To "MSDB" or not to "MSDB". Your choice really. It suits different shops
in different ways but here is a discussion so you can make an informed
choice.

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/extran9/html/17c1de2c-637f-45c2-a148-79294bae0af4.htm

--

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

"tpp" <tpp (AT) discussions (DOT) microsoft.com> wrote

Quote:

Ok, so now I understand that I've to open the packages from SSIS to edit
the
package. When I open BID's do i create a new package and then import it in
that? Also, once I edit the package in SSIS, is it possible to see it in
the
msdb folder for SSIS. Also, which one is better? To save it in msdb or
file
system now?

#9

Hey Allan. Thank you for your help so far. This is what I did to get what you
said. First I created a new SSIS project. Then I deleted the dtsx file it
created inside the project. Then I right clicked 'SSIS Packages' and clicked
'Add Existing PAckage' Then, I saw the dts packages from there and now can
edit it. But is the first part necessary where I've to create a new project
and delete the dtsx file and then do my stuff? Am I doing this right?

Thank you very much, Allan.

#10

If you want to be able to get the richness of the debug VS environment and
test the changes yes. If you simply want to change your package and put it
back with no testing then you can just look at it in VS.

File | Open

You do not have to remove the original package. You can have as many as you
want in there. I am on a project now where I have 350 in there.

--

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

"tpp" <tpp (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hey Allan. Thank you for your help so far. This is what I did to get what
you
said. First I created a new SSIS project. Then I deleted the dtsx file it
created inside the project. Then I right clicked 'SSIS Packages' and
clicked
'Add Existing PAckage' Then, I saw the dts packages from there and now can
edit it. But is the first part necessary where I've to create a new
project
and delete the dtsx file and then do my stuff? Am I doing this right?

Thank you very much, Allan.