is there a way to safely run the most recent version of a
package, without using GUID ? Having to cut-and-paste from
DTSRUNUI is not the best approach in a corporate
environment, where automation and segragation of duties is
a must.

I've run a few tests with
DTSRUN /S svr /E /N pkg

With Sql 2000 client, the above always executes the latest
version of my package. Has there been a rpevious bug with
7.0 clients ? I'm worried to see both the documentation
and the Chaffin book consistently recommend messing with
those long strings.

Andrew

I *NEVER* use it. I always want the latest version when I run it from the
cmd line like this.

--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Andrew Schonberger" <andrewsc (AT) internode (DOT) no.spam.on.net> wrote

Is the GUID transportable accross servers ? Consider a
formal environment, where we need to describe, in advance,
all steps to be taken during production release.

During release, we copy the package from a Test Sql server
to a Production Sql server. Assume I've generated the
command line from DTSRUNUI in Test. If we change the /S
server argument, would the rest of the command line remain
valid to run in Prod ?

How have you moved it?

if you used "Save As" then no you will generate new ids.

If you pumped straight into the sysdtspackages tables then this should
preserve them.


--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

<anonymous (AT) discussions (DOT) microsoft.com> wrote