DTS Execution :: Who, When and WHERE ?? | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

DTS Execution :: Who, When and WHERE ??

When it comes to security in DTS, I have read http://support.microsoft.com/default.aspx?scid=kb;en-us;282463 and it gives some clues about DTS packaging (security) but nothing is said about which users have the right to execute them and how to set up an environment with multiple users designing and executing shared packages …. I know nothing about how to change DTS’s owners, should that be the reason ??? probably I have to study more the inner nature of the DTS’s¿¿¿ thanks for the help
For multi-user environment, I followed:
If you save DTS packages with an owner password and a user password, then you can limit users to only executing the package by providing them only the user password. You can use the owner password for making changes to the package and also to execute the package. You can then use the user password only to execute the package. Using the user password to execute the package prevents users from making modifications to the package. Enable auditing through the SQL Profiler to see who is creating packages and deny those users further attempts to create packages.
HTH Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
satya, u said :
"
You can use the owner password for making changes to the package and also to execute the package. You can then use the user password only to execute the package. Using the user password to execute the package prevents users from making modifications to the package.
" yes, that is what the article tells us …. the problem is DEVELOPER_1 and DEVELOPER_2 being able to make changes and at the same time execute the package….. the article says the only way is to save it as follows :: (sic) "
When you save a package to Meta Data Services, the DTS package protection options are not available. However, one advantage of saving packages to the repository is that it enables users to use the built-in versioning feature. Packages are saved with a versionid that displays as the different datetimes the package is opened and saved.
"

yes, that is what the article tells us …. the problem is DEVELOPER_1 and DEVELOPER_2 being able to make changes and at the same time execute the package…..
Any chance of avoiding same time modification of a DTS package? And with regard to the saving the package and version control, it is only the way.
Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>