March 25, 2008 at 9:46 am
In 2000 we were able to open any owner's package, modify it and just click save. In 2005 we are unable to do this. I don't want to open and 'save as' because that will create way toooooo many dts packages, and dont want to lose the history either.
I've read about using a sql server login. However, that is also not an option for dba manager. Any ideas?????
¤ §unshine ¤
March 25, 2008 at 10:33 am
Is this for DTS packages that you have put on a SQL 2005 server or SSIS packages?
March 25, 2008 at 10:48 am
We're talking about legacy DTS package, right? Members of Sysadmin and package owners can still save versions of packages in SSMS. Others would have to have execute permissions on the dts stored procedures in msdb.
Greg
March 25, 2008 at 12:06 pm
Yes, this is the Legacy DTS Packages on sql server 2k5. If they are db_owner, do they still need that permission?
¤ §unshine ¤
March 26, 2008 at 9:01 am
Maybe if they're members of db_owner in msdb, but I haven't tried that. Permissions in msdb don't work exactly like those in user databases.
Greg
March 27, 2008 at 9:48 am
Rather than beating my head over this, I did the "unorthadoxed" and changed the system stored proc sp_add_dtspackage.
¤ §unshine ¤
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply