Is there a way to give customers access to SSIS? They need to be able to create their own SSIS packages. Of course we have more then one customer so it would be nice to have modular security in place where they don't get to see customers abc and customer xyz packages. Only their own.
thanks!
Well, sure. But the only way I know of is to buy and install the SQL Server 2005 client tools, since the SSIS designer is essentially Visual Studio. I don't know if there is a SKU for just the client tools though, or if you have to buy one of the SQL Server editions.This page on MSDN has some information about the various editions.
You might check the licensing to see if you can give access to SSIS through Terminal Services, if that makes sense for your environment. But I'm betting that they'll need their own copy of the client tools to use locally.
And SQL Server 2005 has very granular security. It may take some thought and a little effort to get set up the way you need it, but you should be able to secure almost any scenario you encounter.
Don
|||but how? when I connect as the sysadmin to SSIS there is no way to create users and set permissions. Do you set the permissions in a different location?
|||You can set permissions using Management Studio, another of the client tools. Or you can write T-SQL code to do the same thing and run it either using the command line SQLCMD tool or through Management Studio.
But I'm not sure I understand. You aren't saying that you want your clients to create users and set permissions, are you? That's an admin function that should be tightly controlled.
Anyway, two different operations, two different tools.
Does that clarify?
Don
|||In SSIS packages you can provide the security information. Use the property
EncryptAllWithPassword of a dtsx packages. This will allow the user to open or execute the package with the password. Niether they will be able to see the package without the password.
So basically based on customer you can create password and then you can provide them the respective password.
|||
What I am trying to say is this:
Customer A is an admin on his database, nowhere else. I need to be able to give customer A the ability to create SSIS packages for his database. At the same time I don't need him to be able to modify other peoples SSIS packages.
So, where do I set the permissions to give him the ability to create SSIS packeges?
|||The SSIS packages can be developed regardless of the Sql server. Its not must to have the SQL Server installed on the same machine to develop package.
Also you can save SSIS packages in two ways one if after you created a SSIS packages you can export it to SQL Server Storage or you can save it on File System as well. Both way you will be able to execute the packages.
There is no need to give any one ability to create SSIS packages. He/She can create packages on his/her machine. So that no person will be able to see others packages because they will be on there machine also.
Please read the link... it will help you to do what you want
http://www.microsoft.com/technet/prodtechnol/sql/2005/mgngssis.mspx
No comments:
Post a Comment