 | |
HowTo Transfer DTS Packages from SQL 2000 STD and SQL 2000 Ent
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
HowTo Transfer DTS Packages from SQL 2000 STD and SQL 2000 Ent -
06-11-2008
, 07:56 PM
#2
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
#3
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
#4
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
#5
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
#6
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
#7
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
#8
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
#9
| |||
| |||
|
|
I tried to transfer the Packages in SQL 2000 STD to SQL 2000 Ent by Backup and Restore. It wouldn't allow and come up with error. Is there any way to transfer the packages? Is there any robust way to migrate to SQL 2005 Integration services? |
DTSs are phisically stored in the msdb database. Did you tried backup
and restore of this database?
Nevertheless msdb database should contain other infos (related to the
specific server), therefore i'm not sure it will work fine.
Some time ago I faced this problem. I had to move a bunch of packages
(about 20) from one sql2000 to another (i don't think it's important
if they're enterprise, standard...). Well... i moved them using "save
as" from the package menu, one by one...
Probably it isn't the quickest way to do it, but it worked.
In SSIS there's a task that allows execution of legacy dts packages.
But, for what i know, once migrated to sql2005 you can't either open
or modify them anymore: at least you can't do it with the old sql2000
GUI.
For a robust migration from DTS to SSIS, there are some commercial
tools. Can't tell anymore.
Bye,
M.
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.