having a contractor develop SSIS packages and security issues

Hi Guys,

I will have a constractor for 3 months developing ssis packages for me.

Obviously, his Windows account will be deleted when he leaves.

My question his. under which securoty context should he develop packages so they will still work and still be accessible after his departure. Assuming we do not want to use any password to either have his packages running or have his packages accessible by other developers from the development environment.

Most of all we do not want ANY job failure due to "encryption issues" after his departure

Thanks

Philippe

In a shared enviornment, I like to use package passwords myself. I use a password in development and when we had them off to a client or to production support, they assign a new password to the package. dtutil.exe can do this quickly for you if you generate a batch file.

This may help you to with that type of strategy if you're interested:

http://whiteknighttechnology.com/cs/blogs/brian_knight/archive/2005/12/19/34.aspx

-- Brian Knight

|||

If you store your packages to SQL Server, than you can use roles to grant and deny access to the packages. This is also a great approach if you wish to automatically execute packages because the integrations with Agent, the DTS Subsystem, and proxy accounts is all seamless.

I have an article here about SSIS security :

http://www.windowsitpro.com/Article/ArticleID/46723/46723.html

K

Handling errors in DTS packages

HI!!

I've been working for an year or so with DTS, but it still makes me mad with it's cryptic error messages!!!!

"The task reported failure on execution" is one of the "funny" error messages I retrieve. I've tried with the log option, but error messages stored there are as cryptic as the one shown on the screen!!!!!

Timothy Peterson in "MS SQL Server 2000 DTS" provides code chunks that can be used to "decode" numerical error messages into something readable and understandable, but I really don't realize where should I put that code :( It seems to work only if you are executing packages via Visual Basic, and not using the MMC

That's it, I really do need help with this!!!!!!! I beleive that there's someone out there that had faced and solved this problem !

Thanks in advance
lorenaWhy do you have to use DTS?|||I'm working on an ETL process for a Data Warehouse
Oracle "holds" the source databases and the DW is implemented on SQL Server 2000.


Originally posted by Brett Kaiser
Why do you have to use DTS?