| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
|
| Currently I have two SQL servers that need SSIS packages run against them to upload data from excel or access. The preferred method is to have an end user start the process. On one server, the SSIS file package is run by starting a SQL job, which has access to a file server to access the excel file. The second SQL server is across another domain and the SQL server user can not access the file server, so I need another method. Ideally I would like the user to initiate SSIS packages without having to load SSIS services on their machine, which DTEXEC needs. Is there a better way to do this? Thanks Dwight |
|
#2
|
| Can you use a batch file somewhere that would copy the "non-accessable" excel file to a server the second SQL server would have permissions to access? You could use Powershell scripts to do this, as Powershell has the ability to authenticate in an encrypted fashion and thus may be able to copy the file accross a domain. Dennis "Dwight" news:ef2e6827-35e1-4536-8f12-7cbefa3f00fb-at-56g2000hsm.googlegroups.com... > Currently I have two SQL servers that need SSIS packages run against > them to upload data from excel or access. The preferred method is to > have an end user start the process. On one server, the SSIS file > package is run by starting a SQL job, which has access to a file > server to access the excel file. The second SQL server is across > another domain and the SQL server user can not access the file server, > so I need another method. > > Ideally I would like the user to initiate SSIS packages without having > to load SSIS services on their machine, which DTEXEC needs. Is there a > better way to do this? > > Thanks > Dwight |
![]() |
| Thread Tools | |
| Display Modes | |