DTS Scripts

We are upgrading our current SQL2000 Server to new hardware. Is there a way
to transfer DTS packages from one server to another. Thanks.
Open the package, in the package menu, select save as...you can save it to
file or directly to another server
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uq4MB3IuFHA.3568@.TK2MSFTNGP10.phx.gbl...
> We are upgrading our current SQL2000 Server to new hardware. Is there a
> way
> to transfer DTS packages from one server to another. Thanks.
>
|||did you hear "Tom Reis" <reistom@.cdnet.cod.edu> say in
news:uq4MB3IuFHA.3568@.TK2MSFTNGP10.phx.gbl:

> We are upgrading our current SQL2000 Server to new hardware. Is there
> a way to transfer DTS packages from one server to another. Thanks.
>
http://www.sqldts.com/default.aspx?204
Neil MacMurchy
http://spaces.msn.com/members/neilmacmurchy
http://spaces.msn.com/members/mctblogs
|||HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default...b;en-us;314546
AMB
"Tom Reis" wrote:

> We are upgrading our current SQL2000 Server to new hardware. Is there a way
> to transfer DTS packages from one server to another. Thanks.
>
>
|||Hi,
Just open the DTS Package and save the package in text file it will be
saved as ii.DTS.
Copy that to another server and open the package and save in local
machine.
hope this help u
from
Doller
sqlsql

DTS Scripts

We are upgrading our current SQL2000 Server to new hardware. Is there a way
to transfer DTS packages from one server to another. Thanks.Open the package, in the package menu, select save as...you can save it to
file or directly to another server
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uq4MB3IuFHA.3568@.TK2MSFTNGP10.phx.gbl...
> We are upgrading our current SQL2000 Server to new hardware. Is there a
> way
> to transfer DTS packages from one server to another. Thanks.
>|||did you hear "Tom Reis" <reistom@.cdnet.cod.edu> say in
news:uq4MB3IuFHA.3568@.TK2MSFTNGP10.phx.gbl:

> We are upgrading our current SQL2000 Server to new hardware. Is there
> a way to transfer DTS packages from one server to another. Thanks.
>
http://www.sqldts.com/default.aspx?204
Neil MacMurchy
http://spaces.msn.com/members/neilmacmurchy
http://spaces.msn.com/members/mctblogs|||HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/defaul...kb;en-us;314546
AMB
"Tom Reis" wrote:

> We are upgrading our current SQL2000 Server to new hardware. Is there a wa
y
> to transfer DTS packages from one server to another. Thanks.
>
>|||Hi,
Just open the DTS Package and save the package in text file it will be
saved as ii.DTS.
Copy that to another server and open the package and save in local
machine.
hope this help u
from
Doller

DTS Scripts

We are upgrading our current SQL2000 Server to new hardware. Is there a way
to transfer DTS packages from one server to another. Thanks.Open the package, in the package menu, select save as...you can save it to
file or directly to another server
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uq4MB3IuFHA.3568@.TK2MSFTNGP10.phx.gbl...
> We are upgrading our current SQL2000 Server to new hardware. Is there a
> way
> to transfer DTS packages from one server to another. Thanks.
>|||did you hear "Tom Reis" <reistom@.cdnet.cod.edu> say in
news:uq4MB3IuFHA.3568@.TK2MSFTNGP10.phx.gbl:
> We are upgrading our current SQL2000 Server to new hardware. Is there
> a way to transfer DTS packages from one server to another. Thanks.
>
http://www.sqldts.com/default.aspx?204
--
Neil MacMurchy
http://spaces.msn.com/members/neilmacmurchy
http://spaces.msn.com/members/mctblogs|||HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546
AMB
"Tom Reis" wrote:
> We are upgrading our current SQL2000 Server to new hardware. Is there a way
> to transfer DTS packages from one server to another. Thanks.
>
>|||Hi,
Just open the DTS Package and save the package in text file it will be
saved as ii.DTS.
Copy that to another server and open the package and save in local
machine.
hope this help u
from
Doller

DTS question

Ok, i have a set of foxpro tables and a SQL 2000 db.

i'm trying to move a table of data from the fox to the sql2000.

I'm using dts to point a connection to a particular table in fox, and setting the destination to my sql database.

i select 'create table' and it makes the table in sql for me.

i click on the transformations tab, and it sets up the transforms. no problem.

when i execute, i'm getting these generic errors ('cannot convert data type') or some such bs. the error does not tell me WHAT TRANSFORMATION or what source field is causing the problem.

so i manually went and eliminated each dts transform (one at a time) and ran till i found the offending dts transform.

so i figured this one out.

here's my question:

WHAT A PAIN IN THE BUTT! what can i do to get dts to tell me what friggin transform is the offending transform?

I've got several HUNDRED tables to convert yet, and if i have to do this again i'm going to jump off a tall building.

there's got to be a better way...When we moved our data from Visual FoxPro into SQL Server we used the Upsize Wizard from within Visual FoxPro. It was pretty painless (although I believe we had to add all of the free tables to a database). Would this work for you?

Terri

DTS Legacy and SQL 2005

I am in the process of migrating to a new SQL 2005 server. I have a number of DTS packages on my SQL2000 server, approximately 200, that are used on a daily basis. I used the migration wizard to migrate the packages from the 2000 server to the new 2005 server however there are issues with the way some were brought over. I would like to have all of the packages moved from the 2000 to the 2005 server and appear under Legacy DTS so that I can run them as 2000 DTS packages unitl I have a chance to correct the issues.

Here is where my question lies. The migration wizard migrates upgrades all of the packages. How do I move them from the one server to the other and perserve their 2000 DTS format? The servers are on 2 separate boxes with different instance names. Everything I've read tells you how to run the legacy packages but nothing seems to explain on to move them.

Any help would be appreciated

Pete

As you have found the migration wizard attempts to create new SSIS 2005 packages from your DTS packages. Due to the fundamentally different architecture this can be limited in its success.

Moving your DTS 2000 packages to a new server, should be effectively the same as moving DTS packages between 2000 servers, so the following information may still be valid: http://www.sqldts.com/default.aspx?204

However, note that I have not tested this scenario - it is only a suggestion and would need some testing and experimentation.

Donald

|||

Maybe not very polite, but what the heck! why you want migrate them to Sql25k instead of make them from the beginning taking advantatge of all that native stuff?

We've got around 500 and most of them on-daily basis. We have come to the conclusion that left the old ones inside a rubbish.

|||

Although, of course we're talking about bank sector...Thing going here slower

I suppose that if you have mainly DTS packages with the usual tasks (pumping, sql tasks, vbScript and nothing else) migration could be successful from Sql25k otherwise if you have DTS with custom tasks it might not easier.

DTS in SQL 2005

Not sure why Microsoft would remove from SQL 2005 DTS import data
sources all the default drivers available to ODBC but they did. In SQL
2000 the drivers available to ODBC were by default available to DTS
import. How does one go about getting DTS to recognize these drivers
so simple data import can be accomplished.
To import from a DBF file you now have to create an ODBC data source
Every time you want to add a new file and then to add insult to injury
they make you key in all the ODBC information for the import source
instead of giving you a simple drop down.
Seems like a huge step backwards as far as user interface goes.
Hi
If I understood you correctly , you can run DTS (SS2000) from SS2005. There
is a folder called Legacy under Management folder.
<jmirsky@.hotmail.com> wrote in message
news:1139956308.785445.51930@.g43g2000cwa.googlegro ups.com...
> Not sure why Microsoft would remove from SQL 2005 DTS import data
> sources all the default drivers available to ODBC but they did. In SQL
> 2000 the drivers available to ODBC were by default available to DTS
> import. How does one go about getting DTS to recognize these drivers
> so simple data import can be accomplished.
> To import from a DBF file you now have to create an ODBC data source
> Every time you want to add a new file and then to add insult to injury
> they make you key in all the ODBC information for the import source
> instead of giving you a simple drop down.
> Seems like a huge step backwards as far as user interface goes.
>

DTS in SQL 2005

Not sure why Microsoft would remove from SQL 2005 DTS import data
sources all the default drivers available to ODBC but they did. In SQL
2000 the drivers available to ODBC were by default available to DTS
import. How does one go about getting DTS to recognize these drivers
so simple data import can be accomplished.
To import from a DBF file you now have to create an ODBC data source
Every time you want to add a new file and then to add insult to injury
they make you key in all the ODBC information for the import source
instead of giving you a simple drop down.
Seems like a huge step backwards as far as user interface goes.Hi
If I understood you correctly , you can run DTS (SS2000) from SS2005. There
is a folder called Legacy under Management folder.
<jmirsky@.hotmail.com> wrote in message
news:1139956308.785445.51930@.g43g2000cwa.googlegroups.com...
> Not sure why Microsoft would remove from SQL 2005 DTS import data
> sources all the default drivers available to ODBC but they did. In SQL
> 2000 the drivers available to ODBC were by default available to DTS
> import. How does one go about getting DTS to recognize these drivers
> so simple data import can be accomplished.
> To import from a DBF file you now have to create an ODBC data source
> Every time you want to add a new file and then to add insult to injury
> they make you key in all the ODBC information for the import source
> instead of giving you a simple drop down.
> Seems like a huge step backwards as far as user interface goes.
>

DTS imput oke, but the job failed

Who can help me.
I'm working with SQL2000 server
and i'm using DTS import.
I have made a schedule package (job) from a DTS.
When i run the DTS manual there is no problem, it works
But when i run the job, it failed.
But some other jobs to import a DTS there is no problem.
Who can help me.Jaap,
Look at this KB: http://support.microsoft.com/?kbid=269074
--
Regards,
Rodrigo Fernandes
"Jaap" wrote:
> Who can help me.
> I'm working with SQL2000 server
> and i'm using DTS import.
> I have made a schedule package (job) from a DTS.
> When i run the DTS manual there is no problem, it works
> But when i run the job, it failed.
> But some other jobs to import a DTS there is no problem.
> Who can help me.

DTS imput oke, but the job failed

Who can help me.
I'm working with SQL2000 server
and i'm using DTS import.
I have made a schedule package (job) from a DTS.
When i run the DTS manual there is no problem, it works
But when i run the job, it failed.
But some other jobs to import a DTS there is no problem.
Who can help me.
Jaap,
Look at this KB: http://support.microsoft.com/?kbid=269074
Regards,
Rodrigo Fernandes
"Jaap" wrote:

> Who can help me.
> I'm working with SQL2000 server
> and i'm using DTS import.
> I have made a schedule package (job) from a DTS.
> When i run the DTS manual there is no problem, it works
> But when i run the job, it failed.
> But some other jobs to import a DTS there is no problem.
> Who can help me.

DTS imput oke, but the job failed

Who can help me.
I'm working with SQL2000 server
and i'm using DTS import.
I have made a schedule package (job) from a DTS.
When i run the DTS manual there is no problem, it works
But when i run the job, it failed.
But some other jobs to import a DTS there is no problem.
Who can help me.Jaap,
Look at this KB: http://support.microsoft.com/?kbid=269074
Regards,
Rodrigo Fernandes
"Jaap" wrote:

> Who can help me.
> I'm working with SQL2000 server
> and i'm using DTS import.
> I have made a schedule package (job) from a DTS.
> When i run the DTS manual there is no problem, it works
> But when i run the job, it failed.
> But some other jobs to import a DTS there is no problem.
> Who can help me.