![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I created a VB.Net appliction that creates and executes a couple of DTS packages. I use trusted connection in my connection objects. I then deployed these applictions to a user's machine. I had to create a login on the SQL server and promote them the the Serve Administrator role so they could run the package from their machine. I would like to know if anybody knows what the minimum settign I can use but still allow them to run the packages? Or maybe change the connection properties? |
#3
| |||
| |||
|
|
In article <553a0349.0308211017.e3005d1 (AT) posting (DOT) google.com>, rwiethorn rwiethorn2002 (AT) yahoo (DOT) com> writes I created a VB.Net appliction that creates and executes a couple of DTS packages. I use trusted connection in my connection objects. I then deployed these applictions to a user's machine. I had to create a login on the SQL server and promote them the the Serve Administrator role so they could run the package from their machine. I would like to know if anybody knows what the minimum settign I can use but still allow them to run the packages? Or maybe change the connection properties? If using a trusted connection, and the package is run from the users desktop then the user must have permissions to do everything, including run all the SQL that is done in the package. Using a trusted connection in DTS is just like in a VB program or similar, the current user is the user that makes the connection, hence they run the SQL. Just remember DTS is a client side application. |
#4
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |