|
I developed an SQL 2005 SSIS package that I want to run from the command line on another computer, when I run the package on my machine, with SQL 2005 Developer installed and VB6, the process runs just fine, but slow (reason we are trying to run on another machine). I have copied over the specific DLLs, but the package still fails to run. I would post the specific error, but the machine died when I attemped to install SQL 2005 Express. Any assistance with determining what needs to be on the remote machine would be greatly appreciated.!
(comments are locked)
|
|
SSIS is not part of SQL Express, nor is it a client type application the way DTS was from SQL 2000. You must run it on a machine upon which one of the full SQL Server editions installed (Developer, Standard, or Enterprise) has been installed. Thanks, John, I kind of figured this was the case, but I was hoping there was an easier softer way around it.
Oct 20 '09 at 09:04 AM
Dave P
(comments are locked)
|
|
If it's a .NET dependency, then you really need to look at the content of the generated exception to look at what module you would need to load. If it's a native dependency, then the Dependency Walker tool will give you a good idea of what DLLs you need.
(comments are locked)
|
|
You can put the dtexec statement in sqlcmd statement and kick it off from remote machine e.g.: Maybe someone can suggest improvements, but this worked for me Regards, Khalid Dhariwal
(comments are locked)
|
