200 DTS and SQLServer 2005

[Jonathan Crawford]

Hi

I am sorry if you have heard this one before.
We have had full SQL Server 2000 for years
but are migrating to a new webserver SQL Server 2005 Workgroup.

I have a very large dts which checks data and moves it from one database to
another.
I managed to import this into legacy and installed something that will let
me reconfigure it.

However it does not seem to be possible to run the legacy dts from the
scheduler.

I discovered that I could right click on the dts and select migrate and it
would create a package somewhere
which I could access (I say somewhere as these don't seem to be editable)

The problem I have is that the modification fails very time on my principal
dts because it has square brackets in the names of the steps.
This is because the default naming of the 2000 dts put is in automatically.
eg [dbo].[webtable]. I don't have a means of changing these step names.
The only way I can see them is by exporting the dts as a bas
I can't believe that anyone in their right mind would have created such a
mess.


So my question is
a) is there anyway of getting a dts to run on a scheduler in SQL Server Work
group on a 64 bit machine
b) how can rename a step in a dts (please don't say rebuild it as it is a
major bit of work and I would
rather migrate the whole thing to LAMP)


thanks

jc

[Todd C]

Have you tried downloading the legacy components for SQL 2005? (free from
MS)They should let you edit DTS packages stored in a 2005 instance.

Also, it sounds like your issue might be with the QUOTED IDENTIFIERS option.
Not sure how that plays into DTS design or server or database level behaviour
but it might be worth a scan through BOL.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]

Post by Jonathan Crawford
Hi
I am sorry if you have heard this one before.
We have had full SQL Server 2000 for years
but are migrating to a new webserver SQL Server 2005 Workgroup.
I have a very large dts which checks data and moves it from one database to
another.
I managed to import this into legacy and installed something that will let
me reconfigure it.
However it does not seem to be possible to run the legacy dts from the
scheduler.
I discovered that I could right click on the dts and select migrate and it
would create a package somewhere
which I could access (I say somewhere as these don't seem to be editable)
The problem I have is that the modification fails very time on my principal
dts because it has square brackets in the names of the steps.
This is because the default naming of the 2000 dts put is in automatically.
eg [dbo].[webtable]. I don't have a means of changing these step names.
The only way I can see them is by exporting the dts as a bas
I can't believe that anyone in their right mind would have created such a
mess.
So my question is
a) is there anyway of getting a dts to run on a scheduler in SQL Server Work
group on a 64 bit machine
b) how can rename a step in a dts (please don't say rebuild it as it is a
major bit of work and I would
rather migrate the whole thing to LAMP)
thanks
jc

[sql_noob]

Post by Todd C
Have you tried downloading the legacy components for SQL 2005? (free from
MS)They should let you edit DTS packages stored in a 2005 instance.
Also, it sounds like your issue might be with the QUOTED IDENTIFIERS option.
Not sure how that plays into DTS design or server or database level behaviour
but it might be worth a scan through BOL.
HTH
--
Todd C
[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]

Post by Jonathan Crawford
Hi
I am sorry if you have heard this one before.
We have had full SQL Server 2000 for years
but are migrating to a new webserver SQL Server 2005 Workgroup.
I have a very large dts which checks data and moves it from one database to
another.
I managed to import this into legacy and installed something that will let
me reconfigure it.
However it does not seem to be possible to run the legacy dts from the
scheduler.
I discovered that I could right click on the dts and select migrate and it
would create a package somewhere
which I could access (I say somewhere as these don't seem to be editable)
The problem I have is that the modification fails very time on my principal
dts because it has square brackets in the names of the steps.
This is because the default naming of the 2000 dts put is in automatically.
eg [dbo].[webtable]. I don't have a means of changing these step names.
The only way I can see them is by exporting the dts as a bas
I can't believe that anyone in their right mind would have created such a
mess.
So my question is
a) is there anyway of getting a dts to run on a scheduler in SQL Server Work
group on a 64 bit machine
b) how can rename a step in a dts (please don't say rebuild it as it is a
major bit of work and I would
    rather migrate the whole thing to LAMP)
thanks
jc- Hide quoted text -

- Show quoted text -

have you tried to create a new SSIS project, use the execute DTS task
and point it to the DTS package? i have a 2005 server where i had to
create new DTS packages and this is the way i execute them