November 5, 2012 at 3:08 am
In windows 2008, SQL 2008 R2 , changes made to open DTS packages. But only sysadmin can modify and save package. Developer (dataread and datawrite access in msdb) is able to open, but not able to save the DTS.
only onwer of DTS package "DTSPackage"or a member of the sysadmin role may create new versions of it.
Without giving sysadmin access, how to enable developer to edit and save dts.
November 5, 2012 at 3:25 am
This was removed by the editor as SPAM
November 5, 2012 at 3:29 am
Are you connecting to an SQL2000 database in ssms 2008 or trying to open SQL2000 DTS packages that where deployed to SQL2008 R2?
If its the former then I would suggest setting up a VM machine with SQL 2000 Enterprise manager installed and using that to manage them.
If its the later then I would strongly suggest redeveloping them in SSIS 2008 as this is a depricated feature in 2008r2 and they have very limited support, see http://msdn.microsoft.com/en-us/library/bb500440(v=sql.105).aspx
Also it will be better to redevelop them in SSIS 2008 as SQL 2012 no longer supports these types of packages, see http://technet.microsoft.com/en-us/library/bb500429.aspx
_________________________________________________________________________
SSC Guide to Posting and Best Practices
November 5, 2012 at 3:42 am
These were SQL 2000 DTS packages deployed to SQL 2008 R2. Converting them into SSIS is happening in parallel. But till we get complete SSIS package, we have to run DTS packages in SQL 2008 R2. It is running. But developer unable to save after making changes (able to save in new name). Any temporary fix for that?
November 5, 2012 at 3:48 am
You might be able to install the components BUT I dont know if that will work, see http://msdn.microsoft.com/en-us/library/ms143755(v=sql.105).aspx
_________________________________________________________________________
SSC Guide to Posting and Best Practices
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply