A developer needs to execute an SSIS package from a stored procedure and I do not want to enable xp_cmdshell on SQL 2005.
One suggestion is to have the application invoke dtexec on the client PC, but this would cause the package to be executed on the client and also requires some SSIS components be installed on each client.
Another idea is to configure a Windows Service to execute dtexec, but I do not know the risks of this approach. Any thoughts?
Thanks, DaveI did something like this a long time ago in VB by creating an exe or dll in VB using the CmdExec. I placed the exeutable on the web server and my app call it.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment