I am currently trying to execute my first SSIS package and am having a lot of trouble with (what i believe to be) SQL security. During the development of the package i was testing all my connection managers with the sa account. Now that i have deployed the package i want to use another account with less privelages so that my setup is more secure. I have created a new login which maps to both the database my SSIS package is using and also to the msdb database. I have created a schema and user in each of these databases which i had initially set with minimal rights. This caused certain parts of my package to fail. I then set up the login with a sysadmin server role which worked no problem at all. Finnally i then gave the schema for the user full rights and removed the sysadmin server role. once again the package fail. Surely i can't only be able to run the SSIS package with an account that has a sysadmin role?
Can anyone tell me if i am doing something wrong. The SQL server 2005 security model is so frustrating to get to grips with.
Many thanks in advance,
GrantGot it. I required Bulkadmin in adition to some database specific roles.
I do however now get an error when calling the package from a .Net app. It says that the LoadFromSqlServer method failed sue to the fact that only an owner or sysadmin may create new versions of it.
Is there any way to change the owner of the Package?
Thanks,
Grant
No comments:
Post a Comment