Scheduling 2008 Packages with SQL Agent 2005
-
Hi all,
Having somewhat a debate with some DBAs. I designed an SSIS 2008 package. While I know this can't be installed on a 2005 Integration Server, I do not see any reason why a 2005 SQL Agent job can't just run a 2008 package from file system.
SSIS packages are nothing more than executables in my eyes. If I don't have any SQL Server at all on my machine I can still run a package by double clicking the dstx file (Windows has a built in package runner).
Anyways, I created a job in SQL Agent 2005 which will run the 2008 package from file system. The job sees the package package connections and variables when I am creating it. This leads me to believe that the 2005 job shouldn't have any issues running the package from file system (no different than it just starting an executable file to me). I can't save the job and test it out because I don't have rights to do so. But I was able to create it.
This is where the DBAs come in. I informed them that my job can see the the package properties but they keep telling me that it won't work. It certainly doesn't hurt to test it out in my opinion! Can someone confirm if a 2005 SQL Agent job can run a SSIS 2008 package? Again, I just want to run it from file system (the dstx file). Atleast if someone confirms that it works I can point them here to read this post.
Thanks,
Strick
-
The DTSX files are not executables. It is more like the .doc file, containing description of your work flow. There is no way to execute SQL 2005 packages, unless you install SSIS 2005 engine runtime.
---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply