Re: Too much persisted security

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Personally when I want to make sure that I catch something for every task/step/connection in my package and not have to remember to redo things every time I add something to the package I have an Active Script task that will look through the relevant collections and set the property I want on each of those items. Not pretty but it does work.

--


Allan Mitchell
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
http://www.konesans.com




"JXStern" <JXSternChangeX2R@xxxxxxx> wrote in message news:hucfq2p8i06spjegltm5j08t4sl853hc48@xxxxxxx:

I've been using DTS for years and, is it possible this has been going
on the whole time?

The default settings for both OLEDB and ODBC connections (for ODBC
connection to SQLServer) are for "persist security" to be set True.
You can click the Advanced button on each and set it to 0 (False), but
sometimes further editing of the connection or transforms will cause
the DTS designer to set it back to 1 again.

The problem comes when I shipped the package off to QA, and sp_who
reported it as running ON MY WORKSTATION! Hey what? Apparently it
cached a copy of my workstation name in the connection, and this gets
used (inaccurately but harmlessly) when the app is run on another
platform! Using integrated security. This is also where it insists
on putting "DTS Designer" in the app name, if you override that with
your own name, using the designer sometimes puts its own name back in
that slot, too.

I can put in a dynamic task and explicitly override the "extended
properties" in the ODBC task and/or the persist flags in both kinds of
connections, but what an irritating bug!

Anybody else notice this, and have any better fix???

(SQL2000, obviously)

J.

.

Quantcast