April 27, 2015 at 11:37 pm
I have 2 SSIS packages and 3 SQL scripts (I could make them Stored Procedures if needed) that I need to provide access to for 2 employees. I do not desire to provide these employee RDP access onto the sever. If I were to install SQL client tools onto their workstation, does client tools provide a manner in which I can restrict the users to running only those SSIS packages and scripts/procedures?
I would not wish for those users to be able to access the Database Engine and those associates objects (Databases, SQL Agent, etc) that are in that Object Explorer.
Or is there another manner to allow a user to initiate a SSIS package without access the server on which the SQL Server is running?
Thanks
Doug P.
April 28, 2015 at 10:04 am
from the following link, DTEXEC.EXE looks like a good candidate. you could put the execution string in a batch file that the user could double click to run.
http://www.mssqltips.com/sqlservertip/1775/different-ways-to-execute-a-sql-server-ssis-package/
Can you put the scripts into the ssis package? if not you could also run the scripts (probably easier to put them into stored procedures) using SQLCMD via the same batch file (or a different one if that's what you need.)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply