Re: Could not save on existing DTS
From: Darren Green (darren.green_at_reply-to-newsgroup-sqldts.com)
Date: 05/06/04
- Next message: Darren Green: "Re: trim embedd white space"
- Previous message: Darren Green: "Re: dts call"
- In reply to: The Margolins: "Re: Could not save on existing DTS"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 6 May 2004 19:32:19 +0100
In message <uDumc.151544$Gd3.38474083@news4.srv.hcvlny.cv.net>, The
Margolins <margolin@optonline.net> writes
>Make them members of dbo role in msdb.
>
>"SangHun Jung" <anonymous@discussions.microsoft.com> wrote in message
>news:6CA2F4EB-60D8-43BD-8BE9-4BFF96C147C7@microsoft.com...
>> Once we moved to Active Directory domain (let's call BBB domain) from AAA
>domain, all developers could not modify existing DTSs even though they were
>owner of the DTSs (AAA domain). They get error saying you are not in
>sysadmin role so you could not modify. They can create new DTSs on server
>though.
>> I can not just simply give them system admin role on SQL servers to solve
>this issue. Any suggestions would be appreciated.
>>
>> SangHun Jung
>
Adding dbo membership in msdb is not relevant as by default all users
have access to the required stored procs through public. The problem is
with the checks inside the procedures, whereby only owners, which they
are not any more due to the domain change, or sysadmins can delete or
add a new version (update) a package.
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
- Next message: Darren Green: "Re: trim embedd white space"
- Previous message: Darren Green: "Re: dts call"
- In reply to: The Margolins: "Re: Could not save on existing DTS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|