What's the proper procedure for changing task names to something more
meaningful to users? I'm finding that when I change the name of a task (in
disconnected edit) from 'DTSTask_DTSDataPumpTask_1' to something else, I get
an error running the package because SQL Server can't find the task under
it's old name.

In article <#xEekp#pDHA.1488 (AT) TK2MSFTNGP12 (DOT) phx.gbl>, David Morrison
<me (AT) nospam (DOT) com> writes
to that task by name are also updated. There is only one I know of and
that is on the step object, also shown in Disco Edit, for the TaskName
property.

I always update three properties-

Task
..Name

Step
..Name
..TaskName

The step name property is what you see in the log so that is the most
useful one to change, but I always do all three.

Note if you have workflow as well, then there is another reference to
the step name. On the preceding step the precedence constraints
collection, see the constraint that links to the step you are working
with.
To be honest I remove all workflow before changing names because working
backwards to find the workflow constraints is too much like hard work!

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Thanks Darren. I'll see if that does it.

It sure would be nice if it was possible to set the name at creation instead
of having to go back and change the names that SQL Server arbitrarily
assigns.

"Darren Green" <darren.green (AT) reply-to-newsgroup-only (DOT) uk.com> wrote in
message news:nPqHvQSXJGs$Ewh4 (AT) sqldts (DOT) com...