Running SSIS package for non-dba users

This is a discussion on Running SSIS package for non-dba users within the sqlserver-dts forums in Microsoft SQL Server category; 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 ...

Go Back   Database Forum > Microsoft SQL Server > sqlserver-dts

Database Forums

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 08-21-2008, 05:17 PM
Default Running SSIS package for non-dba users

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
Reply With Quote
  #2  
Old 10-15-2008, 08:14 PM
Default Re: Running SSIS package for non-dba users

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" wrote in message
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


Reply With Quote
Reply


Thread Tools
Display Modes



All times are GMT -4. The time now is 05:21 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Integrated by bbpixel2008 :: jvbPlugin R1013.368.1

Search Engine Friendly URLs by vBSEO 3.1.0
vB Ad Management by =RedTyger=
In an effort to better serve ads to our visitors, cookies are used on Mydatabasesupport.com. For more information, check out our Privacy Policy.