Is there a (n easy) way to find out which DTSpackage is run by a job?
The number given in the jobstep is does not ring a bell.

Tnx,

Hans Brouwer

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

By number I presume you mean either the hex display or the GUID associated
with a package. You can look the GUID up in msdb..sysdtspackages. If it is
the HEX display then the easiest way would be to look at the output of
profiler when executing the job and seeing which package is called.



--

----------------------------

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


"hansje" <hansjes (AT) anonymous (DOT) com> wrote

I guess I'm talking about the hexdisplay. I'll have to use Profiler
then, tho I do not think this is an easy way. It's not complex, but it
takes some doing, and all this on a productionserver...

Is this changed in Yukon, do you know?
Tnx for the info


Hans Brouwer

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

I think it s put there for privacy and protection. Only a sysadmin in v2000
can run profiler so that again protects you. You do not have to have the
package specified like this either. it is the way the cmdline is built when
you just right click the package and specify schedule.

Have a look at DTSRUNUI to help you build your cmdline strings

I cannot see any encryption options for the string in the Yukon version of
what is currently DTSRUN

--

----------------------------

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


"hansje" <hansjes (AT) anonymous (DOT) com> wrote

The hex is encrypted. Do you want to decrypt it very easily? Kind of defeats
the point really. There is a crack available now for this, if you can
compile some C code. It took some time to come out, and I hope Yukon is even
harder if using similar mechanisms.

If you want to read it, then don't encypt it, although I appreciate most
users are not aware that this is what the GUI does.

--
Darren Green
http://www.sqldts.com

"hansje" <hansjes (AT) anonymous (DOT) com> wrote