July 7, 2009 at 2:11 pm
We have a little bit of a unique scenario..we have SSIS installed on a server, however we don't have SQL 2005. Our databases are in SQL 2000.
My question is on automation using SQLAgent. We have SQL agent on with 2000 that we use for our automation. I was wondering, if we develop SSIS packages, can we automate the SSIS jobs by using command line in SQL agent that resides on the 200 server. Will we be able to run the packages through 2000 SQL agent using command line with full server path (where SSIS is installed)?
July 7, 2009 at 2:18 pm
I think the short answer is yes, but I have to admit I think you are in a license violation there.. Unless you also have a SQL 2005 license for that box I think you are out of compliance.
In SQL Agent you will have to use Operating System command lines since Integration Services is not an option. I would probably use DTEXECUI to help build out the command lines to use. If the DTEXEC is in the path then you shouldn't have to use the full path in the command line and all the packages will have to be stored in the file system since you won't have the required structure in the local SQL database to house packages in SQL..
CEWII
July 7, 2009 at 2:30 pm
Thanks!
I just wanted to assure you that we do have SQL server 2005 licenses and are in the process of migrating to 2005, but meanwhile we are trying to use SSIS for all the new projects.
Thanks again!
July 7, 2009 at 5:33 pm
In the end licensing isn't my deal, if you did or did not, it wasn't an issue for me, what I did want to make sure was that you were aware there *might* be an issue. I'm glad to hear you have the appropriate licensing, I always hate to have to bring that up, but MS, like everybody else wants to get paid for their labors..
CEWII
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply