 | |
Re: Could not save on existing DTS
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: Could not save on existing DTS -
05-06-2004
, 12:31 PM
|
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 |
sysadmin role so you could not modify. They can create new DTSs on server
though.
Quote:
|
I can not just simply give them system admin role on SQL servers to solve this issue. Any suggestions would be appreciated. SangHun Jung |
#2
| |||
| |||
|
|
Make them members of dbo role in msdb. "SangHun Jung" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:6CA2F4EB-60D8-43BD-8BE9-4BFF96C147C7 (AT) microsoft (DOT) 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 |
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
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.