Can not modify existing DTS pkgs

#1

Hello, I've got Windows 2000 and SQL2000 server running
Developers could not modify a DTS that other developer created long time ago. They did not have this problem before we migrated to Active Directory domain. Is there any solution for this except put all developer group to sysadmin role

I allowed NT domain Dev group can login to SQL server. Is there any thing I need to setup for this group in order to make a change to existing DTS pkgs

Thank you in advance
SHJ

#2

In message <6A425688-4BAF-4FDF-9CA3-0B0187EA0922 (AT) microsoft (DOT) com>, SangHun
<anonymous (AT) discussions (DOT) microsoft.com> writes

Quote:

Hello, I've got Windows 2000 and SQL2000 server running.
Developers could not modify a DTS that other developer created long
time ago. They did not have this problem before we migrated to Active
Directory domain. Is there any solution for this except put all
developer group to sysadmin role?

I allowed NT domain Dev group can login to SQL server. Is there any
thing I need to setup for this group in order to make a change to
existing DTS pkgs?

Thank you in advance.
SHJ

By implementing a domain you changed the security context your dev's
use, and there are certain checks inside some of the stored procs that
mean you must be a sysadmin to change packages. More info

Package Ownership Issues
(http://www.sqldts.com/default.aspx?212)

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

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

#3

In message <E0CC5484-0B34-4975-9561-CC5A31ECCDF0 (AT) microsoft (DOT) com>, SangHun
<anonymous (AT) discussions (DOT) microsoft.com> writes

Quote:

My goal is let Developers can modify all DTS packages exist on the
server but not give them sysadmin role.
Is there any way that I can make it happen?

SangHun

"If multiple non-sysadmin developers all need to work on the same
package this limitation can cause major problems. One totally
unsupported workaround would be to remove the checks from the stored
procedure. I have implemented this successfully in development
environments where teams all need to work with the same packages,
without any problems."

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

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

#4

In message <F8F0C823-63E9-4FE9-8A4E-909AF1318378 (AT) microsoft (DOT) com>, SangHun
<anonymous (AT) discussions (DOT) microsoft.com> writes

Quote:

Thanks for the link but...
What do you mean by " remove the checks from the stored
procedure"? How can I do that? Please give me steps so I can
duplicate what you have done.

Thanks again.

SangHun

What I mean is to script off and review to the code of the stored
procedures yourself. Edit the T-SQL and then re-create them without the
checks. If you are not confident about what this means then I don't
recommend you do this as it is unsupported, since these are MS supplied
procedures, in which case perhaps you had better call MS Product Support
Services, although I'm not sure what their answer could possibly be.

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

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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Can not modify existing DTS pkgs

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Can not modify existing DTS pkgs - 05-12-2004 , 11:56 AM

Re: Can not modify existing DTS pkgs - 05-12-2004 , 12:47 PM

Re: Can not modify existing DTS pkgs - 05-12-2004 , 01:52 PM

Re: Can not modify existing DTS pkgs - 05-13-2004 , 12:55 AM