minimum req files for a desktop to use DTS?

Hey all,
I have an operator who needs to be able to run a dts package, but I do not want to give them Enetrprise Manager. Is it possible to just install the objects needed to run DTS?Give them osql.exe, create a bat that executes the package...

make sure you can connect and execute with something other than sa, because you'll have to hard code the is and pwd...|||You can write a little vb app to execute the package or just schedule it.|||Look at dtsrun.exe or dtsrunui.exe.|||Originally posted by rnealejr
Look at dtsrun.exe or dtsrunui.exe.

No kidding...

Good one for the memory banks...

I avoid DTS for the most part...

Migration without backup-files *.dts

Hello All,

I have to

migrate SQL 2000 DTS-Packages to SQL 2005. My Problem is that I didn't saved my

DTS-Packages as files and the SQL 2000 Server exist no longer.

Actually I

have only the old hard disk with the SQL 2000 databases. Do you have any ideas

what can I do?

Thanks

Jonas

Jonas1980 wrote:

Hello All,

I have to migrate SQL 2000 DTS-Packages to SQL 2005. My Problem is that I didn't saved my DTS-Packages as files and the SQL 2000 Server exist no longer.

Actually I have only the old hard disk with the SQL 2000 databases. Do you have any ideas what can I do?

Thanks

Jonas

Do you have backups of the databases?|||Yes, I have!|||

Jonas1980 wrote:

Yes, I have!

You may be able to access the DTS packages by restoring the backups to SQL Server 2005.

Check this link for more details: http://msdn2.microsoft.com/en-us/library/ms143706.aspx

|||

I can

restore the databases, e.g. the msdb-database from the hard disk of my old

server. Do you know any possibility to migrate my dts packages that are saved

in the msdb database without a running SQL Server 2000?

|||If using local server packages you can do this. Get the old msdb online, does not have to be called msdb though, just need to mount the DB somehow. Then rip the contents of the sysdtspackages table into a real msdb DB's sysdtspackages table. You can even use DTS or SSIS to do the data transfer or even just a INSERT ... SELECT if both DBs are on the same server.

Migration SQL server 2000 to 2005, with heavy use of DTS

We have a big migration from SQL server 2000 to 2005
It is a big procedure aith millions of records and it uses DTSs
heavily, so I am asking some hints on s your experience on
1. "basic" migration of DB ib itself
2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
supported and that would be a great problem for us
Any reporting of other known issues - small, medium or big -
will be greatly appreciated.
Thank you so muchSeveral things to do, the ones I remember:
1) Check BOL section 'Upgrading to SQL Server 2005', 'Backward
Compatibility'. Look for deprecated and discontinued features, breaking
changes and behavior changes.
2) Use the SQL Server Upgrade Advisor and follow its recommendations
3) You may want to consider moving the DTS packages without converting to
SSIS. Check also 'Upgrading to SQL Server 2005', 'Backward Compatibility' fo
r
DTS.
4) Test everything.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"baruffa66@.gmail.com" wrote:

> We have a big migration from SQL server 2000 to 2005
> It is a big procedure aith millions of records and it uses DTSs
> heavily, so I am asking some hints on s your experience on
> 1. "basic" migration of DB ib itself
> 2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
> supported and that would be a great problem for us
> Any reporting of other known issues - small, medium or big -
> will be greatly appreciated.
> Thank you so much
>|||Hi,
First, if you have not yet done so, get the "Microsoft SQL Server 2005
Upgrade Advisor". You can run this against your SQL Server 2000 server and
it will produce a report on problem areas that you may need to fix. We did
not have much problem, but the old style outer joins (*=, =*) are
deprecated. Also, if you have code that uses system tables some of those
have changed or vanished.
Passwords on 2005 are case-sensitive. This will cause you some problems if
you have code registered to login with a password in a different case from
that stored on the server. (SQL Server 2000 would forgive that, 2005 will
not.)
Since you are DTS heavy, there are "Microsoft SQL Server 2005 Backward
Compatibility Components" and the "Microsoft SQL Server 2000 DTS Designer
Components" to run on SQL Server 2005. Of course, it is the course of
wisdom to upgrade your packages to SSIS prior to SQL Server 2008, but this
can get you into SQL Server 2005 faster, and let you catch up on your DTS
packages one at a time, rather than all at once.
http://technet.microsoft.com/en-us/...aspx#designtime
These additional packages can be found at Feature Pack for Microsoft SQL
Server 2005 - February 2007
a42ec403d17&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en
RLF
<baruffa66@.gmail.com> wrote in message
news:b48d3fdf-2700-4855-b220-7bd616f33e40@.n20g2000hsh.googlegroups.com...
> We have a big migration from SQL server 2000 to 2005
> It is a big procedure aith millions of records and it uses DTSs
> heavily, so I am asking some hints on s your experience on
> 1. "basic" migration of DB ib itself
> 2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
> supported and that would be a great problem for us
> Any reporting of other known issues - small, medium or big -
> will be greatly appreciated.
> Thank you so much|||Ben and Russel,
thanks a lot.
We asked 5 professionals,
4 of them have not even indirect experience on this migration,
the fifth says that he didn't migrate but is using a module of 2005
that allows to keep those oldies but goodies DTS
and launch them from 2005, without migrating to the new SSIS.
Ciao

Migration SQL server 2000 to 2005, with heavy use of DTS

We have a big migration from SQL server 2000 to 2005
It is a big procedure aith millions of records and it uses DTSs
heavily, so I am asking some hints on s your experience on
1. "basic" migration of DB ib itself
2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
supported and that would be a great problem for us
Any reporting of other known issues - small, medium or big -
will be greatly appreciated.
Thank you so muchSeveral things to do, the ones I remember:
1) Check BOL section 'Upgrading to SQL Server 2005', 'Backward
Compatibility'. Look for deprecated and discontinued features, breaking
changes and behavior changes.
2) Use the SQL Server Upgrade Advisor and follow its recommendations
3) You may want to consider moving the DTS packages without converting to
SSIS. Check also 'Upgrading to SQL Server 2005', 'Backward Compatibility' for
DTS.
4) Test everything.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"baruffa66@.gmail.com" wrote:
> We have a big migration from SQL server 2000 to 2005
> It is a big procedure aith millions of records and it uses DTSs
> heavily, so I am asking some hints on s your experience on
> 1. "basic" migration of DB ib itself
> 2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
> supported and that would be a great problem for us
> Any reporting of other known issues - small, medium or big -
> will be greatly appreciated.
> Thank you so much
>|||Hi,
First, if you have not yet done so, get the "Microsoft SQL Server 2005
Upgrade Advisor". You can run this against your SQL Server 2000 server and
it will produce a report on problem areas that you may need to fix. We did
not have much problem, but the old style outer joins (*=, =*) are
deprecated. Also, if you have code that uses system tables some of those
have changed or vanished.
Passwords on 2005 are case-sensitive. This will cause you some problems if
you have code registered to login with a password in a different case from
that stored on the server. (SQL Server 2000 would forgive that, 2005 will
not.)
Since you are DTS heavy, there are "Microsoft SQL Server 2005 Backward
Compatibility Components" and the "Microsoft SQL Server 2000 DTS Designer
Components" to run on SQL Server 2005. Of course, it is the course of
wisdom to upgrade your packages to SSIS prior to SQL Server 2008, but this
can get you into SQL Server 2005 faster, and let you catch up on your DTS
packages one at a time, rather than all at once.
http://technet.microsoft.com/en-us/library/ms143706.aspx#designtime
These additional packages can be found at Feature Pack for Microsoft SQL
Server 2005 - February 2007
http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&displaylang=en
RLF
<baruffa66@.gmail.com> wrote in message
news:b48d3fdf-2700-4855-b220-7bd616f33e40@.n20g2000hsh.googlegroups.com...
> We have a big migration from SQL server 2000 to 2005
> It is a big procedure aith millions of records and it uses DTSs
> heavily, so I am asking some hints on s your experience on
> 1. "basic" migration of DB ib itself
> 2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
> supported and that would be a great problem for us
> Any reporting of other known issues - small, medium or big -
> will be greatly appreciated.
> Thank you so much|||Ben and Russel,
thanks a lot.
We asked 5 professionals,
4 of them have not even indirect experience on this migration,
the fifth says that he didn't migrate but is using a module of 2005
that allows to keep those oldies but goodies DTS
and launch them from 2005, without migrating to the new SSIS.
Ciao

Migration of SQL Serve r2000 packages

Hi,

In SQL Server 2005, when I tried to migrate existing SQL Server 2000 DTS packages using Migration Wizard, I ran into the following error message.

"Index was out of range.Must be non-negative and less than the size of the collection.

Parameter name: index[mscorlib]"

Please help!

Thanks,

KP

Please take a look at this earlier thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130931&SiteID=1
|||Hi there,

Can you describe the problem you're seeing in detail so we can try reproducing it and fixing it?

Thanks,
Silviu

SQL Server team|||

Please check your packages for a space before or (more likely) after the name of the package. This causes the error described.

Unfortunately this problem is not currently detected by Upgrade Advisor when it scans package names for invalid characters.

-Doug

Migration of SQL Serve r2000 packages

Hi,

In SQL Server 2005, when I tried to migrate existing SQL Server 2000 DTS packages using Migration Wizard, I ran into the following error message.

"Index was out of range.Must be non-negative and less than the size of the collection.

Parameter name: index[mscorlib]"

Please help!

Thanks,

KP

Please take a look at this earlier thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130931&SiteID=1|||Hi there,

Can you describe the problem you're seeing in detail so we can try reproducing it and fixing it?

Thanks,
Silviu

SQL Server team|||

Please check your packages for a space before or (more likely) after the name of the package. This causes the error described.

Unfortunately this problem is not currently detected by Upgrade Advisor when it scans package names for invalid characters.

-Doug

Migration of SQL 7.0 package to SQL 2005

Did you try to migrate this package to SQL 2005. The migration process will
migrate the DTS package into SSIS, and encapsulate all functionality it
can't upgrade into mini DTS 2000 packages which will run as subpackages of
the SSIS Package. You can then at your leisure redesign the mini DTS 2000
packages into your SSIS package.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We are migrating from SQL server 7.0 to SQL server 2005.
> In 7.0 I have made a DTS package that does a complex task on pre-scheduled
> times, started by a SQL job.
> This is a brief description of the complex task:
> -Copy files from several computers in the network to a local "working
> directory"
> -Verify the contents of the files (pre-formatted plain text files)
> -Move files with size or content errors to a different directory
> -Load the files that have no errors into a SQL server table (tblImport)
> -Mark records in tblImport that already exist in tblHistory
> -Gather user information about the files that have been succesfully loaded
> into tblImport
> -Create several reports (plain text files) based on the information in the
> files
> -Print the reports to different printers
> -Add the non-marked records in tblImport to tblHistory
> -Delete the non-marked records in tblImport
> -Send e-mails to several recipients with statistical information about the
> task
> This package is made with a number of activex scripts and SQL tasks.
> Because the server this package is running on now is outdated, I have the
> challenge to make this task work in SQL server 2005.
> The database it is using is already transferred to SQL 2005.
> I have seen that creating packages in 2005 is totally different than
> creating packages in 7.0.
> In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can
> only
> load a .dtsx file.
> To me it is ok if I have to build the package in 2005 from scratch or
> build
> it in a totally different way, just as long as it is not taking me too
> much
> time. A different way could be that I copy and paste the scripts and SQL
> statements into several steps of a 2005 job, with some minor changes, but
> I'm not sure if that is a good solution. Especially when something goes
> wrong, I would like to know exactly where things went wrong and what steps
> have to be executed to finish the job.
> Any help or ideas are appreciated!
>
>
Can you save the dts packages as structured storage and then open them up in
SQL 2000 Package Designed and save them there and then try to use the
migration wizard?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...
> Thanks for your response Hilary.
> Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It
> gives
> me an error saying "This SQL Server version (7.0) is not supported."
>
> Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
> will
> news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> pre-scheduled
> loaded
> the
> the
> the
> but
> steps
>

Migration of SQL 7.0 package to SQL 2005

Hi,
We are migrating from SQL server 7.0 to SQL server 2005.
In 7.0 I have made a DTS package that does a complex task on pre-scheduled
times, started by a SQL job.
This is a brief description of the complex task:
-Copy files from several computers in the network to a local "working
directory"
-Verify the contents of the files (pre-formatted plain text files)
-Move files with size or content errors to a different directory
-Load the files that have no errors into a SQL server table (tblImport)
-Mark records in tblImport that already exist in tblHistory
-Gather user information about the files that have been succesfully loaded
into tblImport
-Create several reports (plain text files) based on the information in the
files
-Print the reports to different printers
-Add the non-marked records in tblImport to tblHistory
-Delete the non-marked records in tblImport
-Send e-mails to several recipients with statistical information about the
task
This package is made with a number of activex scripts and SQL tasks.
Because the server this package is running on now is outdated, I have the
challenge to make this task work in SQL server 2005.
The database it is using is already transferred to SQL 2005.
I have seen that creating packages in 2005 is totally different than
creating packages in 7.0.
In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can only
load a .dtsx file.
To me it is ok if I have to build the package in 2005 from scratch or build
it in a totally different way, just as long as it is not taking me too much
time. A different way could be that I copy and paste the scripts and SQL
statements into several steps of a 2005 job, with some minor changes, but
I'm not sure if that is a good solution. Especially when something goes
wrong, I would like to know exactly where things went wrong and what steps
have to be executed to finish the job.
Any help or ideas are appreciated!Did you try to migrate this package to SQL 2005. The migration process will
migrate the DTS package into SSIS, and encapsulate all functionality it
can't upgrade into mini DTS 2000 packages which will run as subpackages of
the SSIS Package. You can then at your leisure redesign the mini DTS 2000
packages into your SSIS package.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We are migrating from SQL server 7.0 to SQL server 2005.
> In 7.0 I have made a DTS package that does a complex task on pre-scheduled
> times, started by a SQL job.
> This is a brief description of the complex task:
> -Copy files from several computers in the network to a local "working
> directory"
> -Verify the contents of the files (pre-formatted plain text files)
> -Move files with size or content errors to a different directory
> -Load the files that have no errors into a SQL server table (tblImport)
> -Mark records in tblImport that already exist in tblHistory
> -Gather user information about the files that have been succesfully loaded
> into tblImport
> -Create several reports (plain text files) based on the information in the
> files
> -Print the reports to different printers
> -Add the non-marked records in tblImport to tblHistory
> -Delete the non-marked records in tblImport
> -Send e-mails to several recipients with statistical information about the
> task
> This package is made with a number of activex scripts and SQL tasks.
> Because the server this package is running on now is outdated, I have the
> challenge to make this task work in SQL server 2005.
> The database it is using is already transferred to SQL 2005.
> I have seen that creating packages in 2005 is totally different than
> creating packages in 7.0.
> In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can
> only
> load a .dtsx file.
> To me it is ok if I have to build the package in 2005 from scratch or
> build
> it in a totally different way, just as long as it is not taking me too
> much
> time. A different way could be that I copy and paste the scripts and SQL
> statements into several steps of a 2005 job, with some minor changes, but
> I'm not sure if that is a good solution. Especially when something goes
> wrong, I would like to know exactly where things went wrong and what steps
> have to be executed to finish the job.
> Any help or ideas are appreciated!
>
>|||Thanks for your response Hilary.
Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It gives
me an error saying "This SQL Server version (7.0) is not supported."
Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
> Did you try to migrate this package to SQL 2005. The migration process
will
> migrate the DTS package into SSIS, and encapsulate all functionality it
> can't upgrade into mini DTS 2000 packages which will run as subpackages of
> the SSIS Package. You can then at your leisure redesign the mini DTS 2000
> packages into your SSIS package.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "a" <a@.b.c> wrote in message
news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> > Hi,
> >
> > We are migrating from SQL server 7.0 to SQL server 2005.
> > In 7.0 I have made a DTS package that does a complex task on
pre-scheduled
> > times, started by a SQL job.
> > This is a brief description of the complex task:
> > -Copy files from several computers in the network to a local "working
> > directory"
> > -Verify the contents of the files (pre-formatted plain text files)
> > -Move files with size or content errors to a different directory
> > -Load the files that have no errors into a SQL server table (tblImport)
> > -Mark records in tblImport that already exist in tblHistory
> > -Gather user information about the files that have been succesfully
loaded
> > into tblImport
> > -Create several reports (plain text files) based on the information in
the
> > files
> > -Print the reports to different printers
> > -Add the non-marked records in tblImport to tblHistory
> > -Delete the non-marked records in tblImport
> > -Send e-mails to several recipients with statistical information about
the
> > task
> >
> > This package is made with a number of activex scripts and SQL tasks.
> > Because the server this package is running on now is outdated, I have
the
> > challenge to make this task work in SQL server 2005.
> > The database it is using is already transferred to SQL 2005.
> > I have seen that creating packages in 2005 is totally different than
> > creating packages in 7.0.
> > In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can
> > only
> > load a .dtsx file.
> > To me it is ok if I have to build the package in 2005 from scratch or
> > build
> > it in a totally different way, just as long as it is not taking me too
> > much
> > time. A different way could be that I copy and paste the scripts and SQL
> > statements into several steps of a 2005 job, with some minor changes,
but
> > I'm not sure if that is a good solution. Especially when something goes
> > wrong, I would like to know exactly where things went wrong and what
steps
> > have to be executed to finish the job.
> >
> > Any help or ideas are appreciated!
> >
> >
> >
> >
>|||Can you save the dts packages as structured storage and then open them up in
SQL 2000 Package Designed and save them there and then try to use the
migration wizard?
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...
> Thanks for your response Hilary.
> Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It
> gives
> me an error saying "This SQL Server version (7.0) is not supported."
>
> Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
>> Did you try to migrate this package to SQL 2005. The migration process
> will
>> migrate the DTS package into SSIS, and encapsulate all functionality it
>> can't upgrade into mini DTS 2000 packages which will run as subpackages
>> of
>> the SSIS Package. You can then at your leisure redesign the mini DTS 2000
>> packages into your SSIS package.
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>> "a" <a@.b.c> wrote in message
> news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
>> > Hi,
>> >
>> > We are migrating from SQL server 7.0 to SQL server 2005.
>> > In 7.0 I have made a DTS package that does a complex task on
> pre-scheduled
>> > times, started by a SQL job.
>> > This is a brief description of the complex task:
>> > -Copy files from several computers in the network to a local "working
>> > directory"
>> > -Verify the contents of the files (pre-formatted plain text files)
>> > -Move files with size or content errors to a different directory
>> > -Load the files that have no errors into a SQL server table (tblImport)
>> > -Mark records in tblImport that already exist in tblHistory
>> > -Gather user information about the files that have been succesfully
> loaded
>> > into tblImport
>> > -Create several reports (plain text files) based on the information in
> the
>> > files
>> > -Print the reports to different printers
>> > -Add the non-marked records in tblImport to tblHistory
>> > -Delete the non-marked records in tblImport
>> > -Send e-mails to several recipients with statistical information about
> the
>> > task
>> >
>> > This package is made with a number of activex scripts and SQL tasks.
>> > Because the server this package is running on now is outdated, I have
> the
>> > challenge to make this task work in SQL server 2005.
>> > The database it is using is already transferred to SQL 2005.
>> > I have seen that creating packages in 2005 is totally different than
>> > creating packages in 7.0.
>> > In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can
>> > only
>> > load a .dtsx file.
>> > To me it is ok if I have to build the package in 2005 from scratch or
>> > build
>> > it in a totally different way, just as long as it is not taking me too
>> > much
>> > time. A different way could be that I copy and paste the scripts and
>> > SQL
>> > statements into several steps of a 2005 job, with some minor changes,
> but
>> > I'm not sure if that is a good solution. Especially when something goes
>> > wrong, I would like to know exactly where things went wrong and what
> steps
>> > have to be executed to finish the job.
>> >
>> > Any help or ideas are appreciated!
>> >
>> >
>> >
>> >
>>
>|||I saved the package as a DTS file and then tried to open it with right
clicking on the Data Transformations Services Folder.
It opened succesfully and an icon was created in DTS folder.
When I right clicked on the icon I had the options to Open, Export, Migrate
or Delete the package.
The Open option showed me a messagebox telling me that the SQL Server 2000
DTS Designer Component need to be installed to edit the package. I
downloaded this designer and installed it. Now I am able to view and edit
the package the way I did in SQL 7.0. But I have not found a way to start
this package on scheduled times with the SQL Jobs. The package can be
started manually from the menu or with the button on the toolbar, so I think
there is a possibillity to start it with an Operating System command.
In SQL 7.0 you can right click a package to schedule it and then an
Operating System command is created to start the package.
The command (for example) then looks like this: (between the dashes)
--
DTSRun /~S 0xDEC29263B482BF0654C6653D6E68736D /~N
0x1787C8739479E8EEE3EDD35BDD12403EAF86F119B7E6BB7D71C055D523BCAF9B80C874A881
ADB6E23669940A342D8A5C13A8FCD425B3C8FA1F469E8326E6839D2B482D22143EC03E /E
--
I don't know exactly what this command does and I also do not know how to
create a similar command in SQL 2005.
Unfortunately in SQL 2005 the option to schedule a package is not available.
I also tried to migrate the package with the Migrate option. It did the
migration job without any errors. So now I can see in the Integration
Services an icon representing the migrated package. But...
When I right click on the icon I do not have an option to view or modify the
package. I can Run the package, but because I cannot check if the migration
is succesfull in my opinion and I can not modify the package, I don't think
I am going to use the migrated package.
So 3 questions are still open:
1 How can schedule the execution of the (original) package? (Probably with
Job running a complex operating System Command, but I don't know how to
create that command)
2 Is there a way to view, modify and schedule the migrated package?
3 How do I create a new package (or something else) that can do similar
tasks like the one I described below. (because there are more packages I
need to migrate to SQL 2005)
Thanks,
John.
Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
news:#ULCMy1MHHA.4912@.TK2MSFTNGP02.phx.gbl...
> Can you save the dts packages as structured storage and then open them up
in
> SQL 2000 Package Designed and save them there and then try to use the
> migration wizard?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "a" <a@.b.c> wrote in message news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...
> > Thanks for your response Hilary.
> > Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It
> > gives
> > me an error saying "This SQL Server version (7.0) is not supported."
> >
> >
> >
> > Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> > news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
> >> Did you try to migrate this package to SQL 2005. The migration process
> > will
> >> migrate the DTS package into SSIS, and encapsulate all functionality it
> >> can't upgrade into mini DTS 2000 packages which will run as subpackages
> >> of
> >> the SSIS Package. You can then at your leisure redesign the mini DTS
2000
> >> packages into your SSIS package.
> >>
> >> --
> >> Hilary Cotter
> >>
> >> Looking for a SQL Server replication book?
> >> http://www.nwsu.com/0974973602.html
> >>
> >> Looking for a FAQ on Indexing Services/SQL FTS
> >> http://www.indexserverfaq.com
> >>
> >>
> >>
> >> "a" <a@.b.c> wrote in message
> > news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> >> > Hi,
> >> >
> >> > We are migrating from SQL server 7.0 to SQL server 2005.
> >> > In 7.0 I have made a DTS package that does a complex task on
> > pre-scheduled
> >> > times, started by a SQL job.
> >> > This is a brief description of the complex task:
> >> > -Copy files from several computers in the network to a local "working
> >> > directory"
> >> > -Verify the contents of the files (pre-formatted plain text files)
> >> > -Move files with size or content errors to a different directory
> >> > -Load the files that have no errors into a SQL server table
(tblImport)
> >> > -Mark records in tblImport that already exist in tblHistory
> >> > -Gather user information about the files that have been succesfully
> > loaded
> >> > into tblImport
> >> > -Create several reports (plain text files) based on the information
in
> > the
> >> > files
> >> > -Print the reports to different printers
> >> > -Add the non-marked records in tblImport to tblHistory
> >> > -Delete the non-marked records in tblImport
> >> > -Send e-mails to several recipients with statistical information
about
> > the
> >> > task
> >> >
> >> > This package is made with a number of activex scripts and SQL tasks.
> >> > Because the server this package is running on now is outdated, I have
> > the
> >> > challenge to make this task work in SQL server 2005.
> >> > The database it is using is already transferred to SQL 2005.
> >> > I have seen that creating packages in 2005 is totally different than
> >> > creating packages in 7.0.
> >> > In SQL 7.0 I can save the packages into a .dts file, but in 2005 I
can
> >> > only
> >> > load a .dtsx file.
> >> > To me it is ok if I have to build the package in 2005 from scratch or
> >> > build
> >> > it in a totally different way, just as long as it is not taking me
too
> >> > much
> >> > time. A different way could be that I copy and paste the scripts and
> >> > SQL
> >> > statements into several steps of a 2005 job, with some minor changes,
> > but
> >> > I'm not sure if that is a good solution. Especially when something
goes
> >> > wrong, I would like to know exactly where things went wrong and what
> > steps
> >> > have to be executed to finish the job.
> >> >
> >> > Any help or ideas are appreciated!
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>|||I have found all the answers myself:
1)
Create a job with the following activex script:
Const DTSSQLStgFlag_UseTrustedConnection = 256
Dim dts
Set dts = CreateObject("dts.Package")
dts.LoadFromSQLServer "MyServer", , , DTSSQLStgFlag_UseTrustedConnection, ,
, , "MyPackage"
dts.Execute
Set dts = Nothing
Make sure that logging is enabled in the package and specify an error log
file.
Actually quite simple!
2 and 3)
In the SQL Server Business Intelligence Development Studio you can create an
Integration Services Project.
From the Project menu select 'Add Existing Package'
Specify where the package can be found. Click Ok. Now the icon of the
package appears in the Solution Explorer.
Right click on the icon of the package and select 'View designer.'
In the designer you can find all the SQL 7.0 options (and much more!) to
edit packages.
a <a@.b.c> wrote in message news:OkVNdF9MHHA.4992@.TK2MSFTNGP04.phx.gbl...
> I saved the package as a DTS file and then tried to open it with right
> clicking on the Data Transformations Services Folder.
> It opened succesfully and an icon was created in DTS folder.
> When I right clicked on the icon I had the options to Open, Export,
Migrate
> or Delete the package.
> The Open option showed me a messagebox telling me that the SQL Server 2000
> DTS Designer Component need to be installed to edit the package. I
> downloaded this designer and installed it. Now I am able to view and edit
> the package the way I did in SQL 7.0. But I have not found a way to start
> this package on scheduled times with the SQL Jobs. The package can be
> started manually from the menu or with the button on the toolbar, so I
think
> there is a possibillity to start it with an Operating System command.
> In SQL 7.0 you can right click a package to schedule it and then an
> Operating System command is created to start the package.
> The command (for example) then looks like this: (between the dashes)
> --
> DTSRun /~S 0xDEC29263B482BF0654C6653D6E68736D /~N
>
0x1787C8739479E8EEE3EDD35BDD12403EAF86F119B7E6BB7D71C055D523BCAF9B80C874A881
> ADB6E23669940A342D8A5C13A8FCD425B3C8FA1F469E8326E6839D2B482D22143EC03E /E
> --
> I don't know exactly what this command does and I also do not know how to
> create a similar command in SQL 2005.
> Unfortunately in SQL 2005 the option to schedule a package is not
available.
> I also tried to migrate the package with the Migrate option. It did the
> migration job without any errors. So now I can see in the Integration
> Services an icon representing the migrated package. But...
> When I right click on the icon I do not have an option to view or modify
the
> package. I can Run the package, but because I cannot check if the
migration
> is succesfull in my opinion and I can not modify the package, I don't
think
> I am going to use the migrated package.
> So 3 questions are still open:
> 1 How can schedule the execution of the (original) package? (Probably with
> Job running a complex operating System Command, but I don't know how to
> create that command)
> 2 Is there a way to view, modify and schedule the migrated package?
> 3 How do I create a new package (or something else) that can do similar
> tasks like the one I described below. (because there are more packages I
> need to migrate to SQL 2005)
> Thanks,
> John.
>
> Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> news:#ULCMy1MHHA.4912@.TK2MSFTNGP02.phx.gbl...
> > Can you save the dts packages as structured storage and then open them
up
> in
> > SQL 2000 Package Designed and save them there and then try to use the
> > migration wizard?
> >
> > --
> > Hilary Cotter
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> >
> >
> >
> > "a" <a@.b.c> wrote in message
news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...
> > > Thanks for your response Hilary.
> > > Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It
> > > gives
> > > me an error saying "This SQL Server version (7.0) is not supported."
> > >
> > >
> > >
> > > Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> > > news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
> > >> Did you try to migrate this package to SQL 2005. The migration
process
> > > will
> > >> migrate the DTS package into SSIS, and encapsulate all functionality
it
> > >> can't upgrade into mini DTS 2000 packages which will run as
subpackages
> > >> of
> > >> the SSIS Package. You can then at your leisure redesign the mini DTS
> 2000
> > >> packages into your SSIS package.
> > >>
> > >> --
> > >> Hilary Cotter
> > >>
> > >> Looking for a SQL Server replication book?
> > >> http://www.nwsu.com/0974973602.html
> > >>
> > >> Looking for a FAQ on Indexing Services/SQL FTS
> > >> http://www.indexserverfaq.com
> > >>
> > >>
> > >>
> > >> "a" <a@.b.c> wrote in message
> > > news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> > >> > Hi,
> > >> >
> > >> > We are migrating from SQL server 7.0 to SQL server 2005.
> > >> > In 7.0 I have made a DTS package that does a complex task on
> > > pre-scheduled
> > >> > times, started by a SQL job.
> > >> > This is a brief description of the complex task:
> > >> > -Copy files from several computers in the network to a local
"working
> > >> > directory"
> > >> > -Verify the contents of the files (pre-formatted plain text files)
> > >> > -Move files with size or content errors to a different directory
> > >> > -Load the files that have no errors into a SQL server table
> (tblImport)
> > >> > -Mark records in tblImport that already exist in tblHistory
> > >> > -Gather user information about the files that have been succesfully
> > > loaded
> > >> > into tblImport
> > >> > -Create several reports (plain text files) based on the information
> in
> > > the
> > >> > files
> > >> > -Print the reports to different printers
> > >> > -Add the non-marked records in tblImport to tblHistory
> > >> > -Delete the non-marked records in tblImport
> > >> > -Send e-mails to several recipients with statistical information
> about
> > > the
> > >> > task
> > >> >
> > >> > This package is made with a number of activex scripts and SQL
tasks.
> > >> > Because the server this package is running on now is outdated, I
have
> > > the
> > >> > challenge to make this task work in SQL server 2005.
> > >> > The database it is using is already transferred to SQL 2005.
> > >> > I have seen that creating packages in 2005 is totally different
than
> > >> > creating packages in 7.0.
> > >> > In SQL 7.0 I can save the packages into a .dts file, but in 2005 I
> can
> > >> > only
> > >> > load a .dtsx file.
> > >> > To me it is ok if I have to build the package in 2005 from scratch
or
> > >> > build
> > >> > it in a totally different way, just as long as it is not taking me
> too
> > >> > much
> > >> > time. A different way could be that I copy and paste the scripts
and
> > >> > SQL
> > >> > statements into several steps of a 2005 job, with some minor
changes,
> > > but
> > >> > I'm not sure if that is a good solution. Especially when something
> goes
> > >> > wrong, I would like to know exactly where things went wrong and
what
> > > steps
> > >> > have to be executed to finish the job.
> > >> >
> > >> > Any help or ideas are appreciated!
> > >> >
> > >> >
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >
>

Migration of SQL 7.0 package to SQL 2005

Hi,
We are migrating from SQL server 7.0 to SQL server 2005.
In 7.0 I have made a DTS package that does a complex task on pre-scheduled
times, started by a SQL job.
This is a brief description of the complex task:
-Copy files from several computers in the network to a local "working
directory"
-Verify the contents of the files (pre-formatted plain text files)
-Move files with size or content errors to a different directory
-Load the files that have no errors into a SQL server table (tblImport)
-Mark records in tblImport that already exist in tblHistory
-Gather user information about the files that have been succesfully loaded
into tblImport
-Create several reports (plain text files) based on the information in the
files
-Print the reports to different printers
-Add the non-marked records in tblImport to tblHistory
-Delete the non-marked records in tblImport
-Send e-mails to several recipients with statistical information about the
task
This package is made with a number of activex scripts and SQL tasks.
Because the server this package is running on now is outdated, I have the
challenge to make this task work in SQL server 2005.
The database it is using is already transferred to SQL 2005.
I have seen that creating packages in 2005 is totally different than
creating packages in 7.0.
In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can only
load a .dtsx file.
To me it is ok if I have to build the package in 2005 from scratch or build
it in a totally different way, just as long as it is not taking me too much
time. A different way could be that I copy and paste the scripts and SQL
statements into several steps of a 2005 job, with some minor changes, but
I'm not sure if that is a good solution. Especially when something goes
wrong, I would like to know exactly where things went wrong and what steps
have to be executed to finish the job.
Any help or ideas are appreciated!Did you try to migrate this package to SQL 2005. The migration process will
migrate the DTS package into SSIS, and encapsulate all functionality it
can't upgrade into mini DTS 2000 packages which will run as subpackages of
the SSIS Package. You can then at your leisure redesign the mini DTS 2000
packages into your SSIS package.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We are migrating from SQL server 7.0 to SQL server 2005.
> In 7.0 I have made a DTS package that does a complex task on pre-scheduled
> times, started by a SQL job.
> This is a brief description of the complex task:
> -Copy files from several computers in the network to a local "working
> directory"
> -Verify the contents of the files (pre-formatted plain text files)
> -Move files with size or content errors to a different directory
> -Load the files that have no errors into a SQL server table (tblImport)
> -Mark records in tblImport that already exist in tblHistory
> -Gather user information about the files that have been succesfully loaded
> into tblImport
> -Create several reports (plain text files) based on the information in the
> files
> -Print the reports to different printers
> -Add the non-marked records in tblImport to tblHistory
> -Delete the non-marked records in tblImport
> -Send e-mails to several recipients with statistical information about the
> task
> This package is made with a number of activex scripts and SQL tasks.
> Because the server this package is running on now is outdated, I have the
> challenge to make this task work in SQL server 2005.
> The database it is using is already transferred to SQL 2005.
> I have seen that creating packages in 2005 is totally different than
> creating packages in 7.0.
> In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can
> only
> load a .dtsx file.
> To me it is ok if I have to build the package in 2005 from scratch or
> build
> it in a totally different way, just as long as it is not taking me too
> much
> time. A different way could be that I copy and paste the scripts and SQL
> statements into several steps of a 2005 job, with some minor changes, but
> I'm not sure if that is a good solution. Especially when something goes
> wrong, I would like to know exactly where things went wrong and what steps
> have to be executed to finish the job.
> Any help or ideas are appreciated!
>
>|||Thanks for your response Hilary.
Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It gives
me an error saying "This SQL Server version (7.0) is not supported."
Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
> Did you try to migrate this package to SQL 2005. The migration process
will
> migrate the DTS package into SSIS, and encapsulate all functionality it
> can't upgrade into mini DTS 2000 packages which will run as subpackages of
> the SSIS Package. You can then at your leisure redesign the mini DTS 2000
> packages into your SSIS package.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "a" <a@.b.c> wrote in message
news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
pre-scheduled[vbcol=seagreen]
loaded[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
but[vbcol=seagreen]
steps[vbcol=seagreen]
>|||Can you save the dts packages as structured storage and then open them up in
SQL 2000 Package Designed and save them there and then try to use the
migration wizard?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...
> Thanks for your response Hilary.
> Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It
> gives
> me an error saying "This SQL Server version (7.0) is not supported."
>
> Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
> will
> news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> pre-scheduled
> loaded
> the
> the
> the
> but
> steps
>|||I saved the package as a DTS file and then tried to open it with right
clicking on the Data Transformations Services Folder.
It opened succesfully and an icon was created in DTS folder.
When I right clicked on the icon I had the options to Open, Export, Migrate
or Delete the package.
The Open option showed me a messagebox telling me that the SQL Server 2000
DTS Designer Component need to be installed to edit the package. I
downloaded this designer and installed it. Now I am able to view and edit
the package the way I did in SQL 7.0. But I have not found a way to start
this package on scheduled times with the SQL Jobs. The package can be
started manually from the menu or with the button on the toolbar, so I think
there is a possibillity to start it with an Operating System command.
In SQL 7.0 you can right click a package to schedule it and then an
Operating System command is created to start the package.
The command (for example) then looks like this: (between the dashes)
--
DTSRun /~S 0xDEC29263B482BF0654C6653D6E68736D /~N
0x1787C8739479E8EEE3EDD35BDD12403EAF86F1
19B7E6BB7D71C055D523BCAF9B80C874A881
ADB6E23669940A342D8A5C13A8FCD425B3C8FA1F
469E8326E6839D2B482D22143EC03E /E
--
I don't know exactly what this command does and I also do not know how to
create a similar command in SQL 2005.
Unfortunately in SQL 2005 the option to schedule a package is not available.
I also tried to migrate the package with the Migrate option. It did the
migration job without any errors. So now I can see in the Integration
Services an icon representing the migrated package. But...
When I right click on the icon I do not have an option to view or modify the
package. I can Run the package, but because I cannot check if the migration
is succesfull in my opinion and I can not modify the package, I don't think
I am going to use the migrated package.
So 3 questions are still open:
1 How can schedule the execution of the (original) package? (Probably with
Job running a complex operating System Command, but I don't know how to
create that command)
2 Is there a way to view, modify and schedule the migrated package?
3 How do I create a new package (or something else) that can do similar
tasks like the one I described below. (because there are more packages I
need to migrate to SQL 2005)
Thanks,
John.
Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
news:#ULCMy1MHHA.4912@.TK2MSFTNGP02.phx.gbl...
> Can you save the dts packages as structured storage and then open them up
in
> SQL 2000 Package Designed and save them there and then try to use the
> migration wizard?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "a" <a@.b.c> wrote in message news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...
2000[vbcol=seagreen]
(tblImport)[vbcol=seagreen]
in[vbcol=seagreen]
about[vbcol=seagreen]
can[vbcol=seagreen]
too[vbcol=seagreen]
goes[vbcol=seagreen]
>|||I have found all the answers myself:
1)
Create a job with the following activex script:
Const DTSSQLStgFlag_UseTrustedConnection = 256
Dim dts
Set dts = CreateObject("dts.Package")
dts.LoadFromSQLServer "MyServer", , , DTSSQLStgFlag_UseTrustedConnection, ,
, , "MyPackage"
dts.Execute
Set dts = Nothing
Make sure that logging is enabled in the package and specify an error log
file.
Actually quite simple!
2 and 3)
In the SQL Server Business Intelligence Development Studio you can create an
Integration Services Project.
From the Project menu select 'Add Existing Package'
Specify where the package can be found. Click Ok. Now the icon of the
package appears in the Solution Explorer.
Right click on the icon of the package and select 'View designer.'
In the designer you can find all the SQL 7.0 options (and much more!) to
edit packages.
a <a@.b.c> wrote in message news:OkVNdF9MHHA.4992@.TK2MSFTNGP04.phx.gbl...
> I saved the package as a DTS file and then tried to open it with right
> clicking on the Data Transformations Services Folder.
> It opened succesfully and an icon was created in DTS folder.
> When I right clicked on the icon I had the options to Open, Export,
Migrate
> or Delete the package.
> The Open option showed me a messagebox telling me that the SQL Server 2000
> DTS Designer Component need to be installed to edit the package. I
> downloaded this designer and installed it. Now I am able to view and edit
> the package the way I did in SQL 7.0. But I have not found a way to start
> this package on scheduled times with the SQL Jobs. The package can be
> started manually from the menu or with the button on the toolbar, so I
think
> there is a possibillity to start it with an Operating System command.
> In SQL 7.0 you can right click a package to schedule it and then an
> Operating System command is created to start the package.
> The command (for example) then looks like this: (between the dashes)
> --
> DTSRun /~S 0xDEC29263B482BF0654C6653D6E68736D /~N
>
0x1787C8739479E8EEE3EDD35BDD12403EAF86F1
19B7E6BB7D71C055D523BCAF9B80C874A881[vbc
ol=seagreen]
> ADB6E23669940A342D8A5C13A8FCD425B3C8FA1F
469E8326E6839D2B482D22143EC03E /E
> --
> I don't know exactly what this command does and I also do not know how to
> create a similar command in SQL 2005.
> Unfortunately in SQL 2005 the option to schedule a package is not[/vbcol]
available.
> I also tried to migrate the package with the Migrate option. It did the
> migration job without any errors. So now I can see in the Integration
> Services an icon representing the migrated package. But...
> When I right click on the icon I do not have an option to view or modify
the
> package. I can Run the package, but because I cannot check if the
migration
> is succesfull in my opinion and I can not modify the package, I don't
think
> I am going to use the migrated package.
> So 3 questions are still open:
> 1 How can schedule the execution of the (original) package? (Probably with
> Job running a complex operating System Command, but I don't know how to
> create that command)
> 2 Is there a way to view, modify and schedule the migrated package?
> 3 How do I create a new package (or something else) that can do similar
> tasks like the one I described below. (because there are more packages I
> need to migrate to SQL 2005)
> Thanks,
> John.
>
> Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> news:#ULCMy1MHHA.4912@.TK2MSFTNGP02.phx.gbl...
up[vbcol=seagreen]
> in
news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
process[vbcol=seagreen]
it[vbcol=seagreen]
subpackages[vbcol=seagreen]
> 2000
"working[vbcol=seagreen]
> (tblImport)
> in
> about
tasks.[vbcol=seagreen]
have[vbcol=seagreen]
than[vbcol=seagreen]
> can
or[vbcol=seagreen]
> too
and[vbcol=seagreen]
changes,[vbcol=seagreen]
> goes
what[vbcol=seagreen]
>

Migration of DTS to SSIS

Well..

Have migrated my SQL 2000 DTS packages to SSIS packages through the package migration Wizard.Also, the hurdle to schedule it as a job has been resolved.But, the concern is the package contains entries\lins for old dataserver.

Is it possible to edit the SSIS pckage using management studio or integration services?

Please move this question to the " SQL Server Integration Services forum" .

Thanks

Migration of DTS to SSIS

Well..

Have migrated my SQL 2000 DTS packages to SSIS packages through the package migration Wizard.Also, the hurdle to schedule it as a job has been resolved.But, the concern is the package contains entries\lins for old dataserver.

Is it possible to edit the SSIS pckage using management studio or integration services?

Please move this question to the " SQL Server Integration Services forum" .

Thanks

Migration of DTS packages to SSIS

I am in a situation where we are redesigning our Datawarehouse. Currently we have our Datawarehouse in SQL 2000 and we are rebuilding from scratch in SQL 2005. This means that even though we will get the same tables but we are planning to rename each & every attribute to make it more meaningful.

The question is like this:

We can migrate the current DTS packages to SSIS but since all the ODBC connections , field names(attributes) will change is it worth it to leverages the DTS packages ?

Also we convert the julian date to gregorian date in our DTS packages but since SSIS has a feature to convert julian date it would be redundant to migrate the packages and my feeling is to create new packages in SSIS and start on a clean slate.

Is there anybody who was in such situation ?

Please advise.

Adarsh Mathur

Personally I would start with a clean slate. I think this will mean you are less likely to use DTS patterns and practices, which are often no longer the most appropriate (assuming they still work), when working in the brave new world of SSIS. Plan your ETL process, define the source to target mappings, and work from that rather using the DTS packages as the template.

Migration from Oracle 7.34 to SQL 2000

I'm attempting to move a database which currently exists on an old Oracle
7.34 instance and tried to use Data Import via DTS to SQL 2000.
The Oracle database consists of views, indexes,packages,triggers as well as
tables structures. I tried DTS using both the ODBC and OLE for Oracle and
only tables and data came over correctly.
Views it appears were converted into tables. Indexes not at all.
I'm using the Oracle 9.2 client on my workstation.
Any ideas on how I might be able to convert this database over from Oracle?
thks
You'll have to move the code, views, etc manually
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Snow" <mrbrew5510@.hotmail.com> wrote in message
news:tea_c.4190$lv3.2047604@.news4.srv.hcvlny.cv.ne t...
> I'm attempting to move a database which currently exists on an old Oracle
> 7.34 instance and tried to use Data Import via DTS to SQL 2000.
> The Oracle database consists of views, indexes,packages,triggers as well
as
> tables structures. I tried DTS using both the ODBC and OLE for Oracle and
> only tables and data came over correctly.
> Views it appears were converted into tables. Indexes not at all.
> I'm using the Oracle 9.2 client on my workstation.
> Any ideas on how I might be able to convert this database over from
Oracle?
>
> thks
>

Migration from Oracle 7.34 to SQL 2000

I'm attempting to move a database which currently exists on an old Oracle
7.34 instance and tried to use Data Import via DTS to SQL 2000.
The Oracle database consists of views, indexes,packages,triggers as well as
tables structures. I tried DTS using both the ODBC and OLE for Oracle and
only tables and data came over correctly.
Views it appears were converted into tables. Indexes not at all.
I'm using the Oracle 9.2 client on my workstation.
Any ideas on how I might be able to convert this database over from Oracle?
thksYou'll have to move the code, views, etc manually
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Snow" <mrbrew5510@.hotmail.com> wrote in message
news:tea_c.4190$lv3.2047604@.news4.srv.hcvlny.cv.net...
> I'm attempting to move a database which currently exists on an old Oracle
> 7.34 instance and tried to use Data Import via DTS to SQL 2000.
> The Oracle database consists of views, indexes,packages,triggers as well
as
> tables structures. I tried DTS using both the ODBC and OLE for Oracle and
> only tables and data came over correctly.
> Views it appears were converted into tables. Indexes not at all.
> I'm using the Oracle 9.2 client on my workstation.
> Any ideas on how I might be able to convert this database over from
Oracle?
>
> thks
>

Migration from DTS to SSIS

Hi everybody,

I would REALLY appreciate it if some had a link to a good tutorial about migration from DTS to SSIS, but without visual studio . net.

For example I need to use DTS package in sql server 2005 and execute them, I used migration wizard (SQL 2005) but it didn't work because i have in my computer sql 2000 et sql 2005 and the server name is PC2, however when i use the server source PC2 and the server destination PC2 an error message appear "server destination should be a sql server 2005 instance ".

help me please..

Thanks very much anyone response my question.

Moving to the SSIS 2005 forum from the SSIS 2008 forum.|||

If the connection is to a computer with both 2000 and 2005 on it, the 2005 install needs to be referenced by the server and instance name (MACHINENAME\INSTANCENAME).

Migration from DTS to SSIS

Hi everybody,

I would REALLY appreciate it if some had a link to a good tutorial about migration from DTS to SSIS, but without visual studio . net.

For example I need to use DTS package in sql server 2005 and execute them, I used migration wizard (SQL 2005) but it didn't work because i have in my computer sql 2000 et sql 2005 and the server name is PC2, however when i use the server source PC2 and the server destination PC2 an error message appear "server destination should be a sql server 2005 instance ".

help me please..

Thanks very much anyone response my question.

Moving to the SSIS 2005 forum from the SSIS 2008 forum.|||

If the connection is to a computer with both 2000 and 2005 on it, the 2005 install needs to be referenced by the server and instance name (MACHINENAME\INSTANCENAME).

Migration exceptions

Hi,
How should one deal with exceptions generated by the DTS to SSIS conversion wizard in sql server 2005?
ThanksWhat exceptions are you getting? That would be a good place to start.

Migration ACCESS --> SQL date field

Hi,
I import an access table with date field in SQL with DTS import/export
wizard.
I got error : data overflow on date field. There is another way to do it ?In the DTS package, transform that column to varchar, and then run isdate()
against the new table to determine which rows need to be repaired.
"Sylvain Provencher" <sylvain.provencher@.nobelia.com> wrote in message
news:uZybbSLpDHA.2268@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I import an access table with date field in SQL with DTS import/export
> wizard.
> I got error : data overflow on date field. There is another way to do it ?
>

Migrating to a new database server

I need to migrate the DTS, the jobs, users and everything from a
database on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to
another (Windows Server 2003, SQL 2000). The databases that do not
already exist on the new server I can restore those from a backup just fine.
The ones that exist (master, model, msdb) I can't copy over from a
restore. It tells me that exclusive access could not be obtained
because the database is in use.
Is there an easy/straightforward way to get everything - especially DTS
and the batch jobs - from my old server to the new one?
Any advice appreciated.
BCSee this post from yesterday: "Moving a DB from 1 Server 2 another".
HTH
Jerry
"Blasting Cap" <goober@.christian.net> wrote in message
news:Ogobt0qeGHA.2456@.TK2MSFTNGP04.phx.gbl...

>I need to migrate the DTS, the jobs, users and everything from a database
>on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to another
>(Windows Server 2003, SQL 2000). The databases that do not already exist
>on the new server I can restore those from a backup just fine.
> The ones that exist (master, model, msdb) I can't copy over from a
> restore. It tells me that exclusive access could not be obtained because
> the database is in use.
> Is there an easy/straightforward way to get everything - especially DTS
> and the batch jobs - from my old server to the new one?
> Any advice appreciated.
> BC
>

Migrating to a new database server

I need to migrate the DTS, the jobs, users and everything from a
database on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to
another (Windows Server 2003, SQL 2000). The databases that do not
already exist on the new server I can restore those from a backup just fine.
The ones that exist (master, model, msdb) I can't copy over from a
restore. It tells me that exclusive access could not be obtained
because the database is in use.
Is there an easy/straightforward way to get everything - especially DTS
and the batch jobs - from my old server to the new one?
Any advice appreciated.
BCSee this post from yesterday: "Moving a DB from 1 Server 2 another".
HTH
Jerry
"Blasting Cap" <goober@.christian.net> wrote in message
news:Ogobt0qeGHA.2456@.TK2MSFTNGP04.phx.gbl...
>I need to migrate the DTS, the jobs, users and everything from a database
>on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to another
>(Windows Server 2003, SQL 2000). The databases that do not already exist
>on the new server I can restore those from a backup just fine.
> The ones that exist (master, model, msdb) I can't copy over from a
> restore. It tells me that exclusive access could not be obtained because
> the database is in use.
> Is there an easy/straightforward way to get everything - especially DTS
> and the batch jobs - from my old server to the new one?
> Any advice appreciated.
> BC
>