March 3, 2011 at 1:43 pm
We have just implemented a dedicated SSIS server on SQL 2008 R2 that only runs SSIS.
The jobs would need to be called from the agent on a SQL 2005 server.
This is the error:
Class not registered . Source: Started: 10:35:29 AM Finished: 10:35:30 AM Elapsed: 1.437 seconds. The package could not be loaded. The step failed.
this is the first time we are calling jobs from a different server, would this be a compatibility issue or are there other considerations for calling jobs on other servers?
March 3, 2011 at 2:52 pm
I didn't realize this until just now, the job is not being executed on the remote 2008 SSIS server it's grabbing the package from the remote server and attempting to run it on the 2005 server. Hence the "class could not be loaded" error.
Now my question is, how do you run an SSIS package on server B when the agent is running on server A? Like I mentioned in my previous post, we don't have the SQL engine / Agent installed on server B.
March 3, 2011 at 3:37 pm
You could use SQL Agent on your 2005 instance to execute a script that uses the WMI Win32_Process class to execute dtexec on the remote server.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 3, 2011 at 3:44 pm
Another option is to create a job on the 2008 server to run the SSIS package. The 2005 server can kick of the job on the 2008 server as required. If the package will always be kicked off from the 2005 server, then you can omit creating a schedule for the job.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
March 4, 2011 at 2:39 am
You could create a .bat script on ServerB that contains a DTEXEC command with parameters.
On ServerA, you execute the .bat script on serverB, passing along the name of the package et cetera as parameters.
On a sidenote: why is this so difficult? It should be easy to run packages on a dedicated SSIS server. More work for Microsoft!
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 4, 2011 at 5:39 am
We are going to install the SQL engine on the new server so we can use the agent. This is a better option since we will have use of the job history which is much easier to use for troubleshooting and job setup is also much easier and quicker.
March 4, 2011 at 5:48 am
Tom Van Harpen (3/4/2011)
We are going to install the SQL engine on the new server so we can use the agent. This is a better option since we will have use of the job history which is much easier to use for troubleshooting and job setup is also much easier and quicker.
Small question regarding license costs:
when you've installed the SSIS stand alone server without the SQL Server Engine, did you already had to pay a license for the entire SQL Server edition?
So I guess that installing the SQL Server engine comes with no extra cost. Am I correct?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 4, 2011 at 7:21 am
Koen Verbeeck (3/4/2011)
Tom Van Harpen (3/4/2011)
We are going to install the SQL engine on the new server so we can use the agent. This is a better option since we will have use of the job history which is much easier to use for troubleshooting and job setup is also much easier and quicker.Small question regarding license costs:
when you've installed the SSIS stand alone server without the SQL Server Engine, did you already had to pay a license for the entire SQL Server edition?
So I guess that installing the SQL Server engine comes with no extra cost. Am I correct?
SSIS, SSAS, or SSRS, alone on a server without the database engine still requires a license, but they may not require the same license. For example, you might need the enterprise edition for one product and standard for another. It's also possible you might want to license one by the number of processors, and another for so many CALS.
Figuring out the best license scheme can be so much fun!!!!!! 😛
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
March 4, 2011 at 8:09 am
I did review the licensing and we can have 1 or all SQL services installed under the same license. I wanted to avoid the extra resource usage so we'll just limit the SQL engine as much as possible.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply