As this article testifies. None usually
Transferring DTS Packages
(
http://www.sqldts.com/Default.aspx?204)
However. Watch out for server connection names. If you explicitly name the
servers as ServerA or ServerB then when you move the package then it will
still be that. If you actually meant for the package to refer to the
(local) server then this nmay not be the case
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com I support PASS - the definitive, global community
for SQL Server professionals -
http://www.sqlpass.org [quoted text, click to view] "Lori Clark" <anonymous@discussions.microsoft.com> wrote in message
news:009f01c39fe5$e533a4c0$a601280a@phx.gbl...
> I apologize if this question appears multiple times, but
> my posts do not seem to appear after I click Send.
>
> I have an existing SQL Server 7.0 and will be upgrading to
> SQL Server 2000 on a different box. I need to get the
> packages from 7.0 to 2000 without having to open each one
> manually and save as a text file or save as to the other
> server. I have created a Linked Server on the 7.0 box and
> issued the following query:
>
> insert into sql7server.msdb.dbo.sysdtspackages
> (name, id, versionid, description, categoryid, createdate,
> owner, packagedata, owner_sid)
> select name, id, versionid, description, categoryid,
> createdate, owner, packagedata, owner_sid from
> sql2k.msdb.dbo.sysdtspackages
>
> The records were added successfully and I can see the
> package in Enterprise Manager.
>
> Does anyone know of any issues of doing this?
>
> Thank you,
> Lori Clark
>
>