![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Joe, In networking, this is bad news because when you delete a User Account, you delete the SID (Security Identifier) that goes along with it. The SID is what gets passed around when determining permissions on various resources like files & folders, etc. Likewise, each DTS package has an owner_sid that is stored in sysdtspackages table in msdb DB. I haven't tried it, but perhaps you can UPDATE owner & owner_sid columns of that particular package (in sysdtspackages) to someone else, like yourself. Maybe that will unlock it enough to SAVE AS something else. Let us know how you make out. Thomas Bradshaw MyWebGrocer.com Data Integration Services -- Message posted via SQLMonster.com http://www.sqlmonster.com/Uwe/Forums...r-dts/200510/1 |
#5
| |||
| |||
|
|
Thanks, This seemed to work. I misspoke before I didn't remove the user from the DB, he were an SA, I removed him from the server role, and removed him from all the DBs he had access to. I never remove users from the server, because there are history tables that may need to reference ex-employees. Thanks again, joe "Thomas Bradshaw via SQLMonster.com" wrote: Joe, In networking, this is bad news because when you delete a User Account, you delete the SID (Security Identifier) that goes along with it. The SID is what gets passed around when determining permissions on various resources like files & folders, etc. Likewise, each DTS package has an owner_sid that is stored in sysdtspackages table in msdb DB. I haven't tried it, but perhaps you can UPDATE owner & owner_sid columns of that particular package (in sysdtspackages) to someone else, like yourself. Maybe that will unlock it enough to SAVE AS something else. Let us know how you make out. Thomas Bradshaw MyWebGrocer.com Data Integration Services -- Message posted via SQLMonster.com http://www.sqlmonster.com/Uwe/Forums...r-dts/200510/1 |
![]() |
| Thread Tools | |
| Display Modes | |
| |