![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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 |
#4
| |||
| |||
|
|
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 |
#5
| |||
| |||
|
|
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 |
#6
| |||
| |||
|
|
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 |
#7
| |||
| |||
|
|
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 |
#8
| |||
| |||
|
|
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 |
#9
| |||
| |||
|
|
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 | |
| |