June 3, 2013 at 1:49 pm
You've hit pretty much all the nails on the head for this. You either need to license a server to your job server, or run it via a foreign call to dtexec, which is only available via windows scheduler if you're not purchasing/installing more software.
There are other scheduling softwares out there that are relatively cheap that you could give the DBA's access to without opening up windows scheduler if you wanted, and they are worth a day or so of investigation just to know what's available.
But, basically, yeah. You're screwed. It's part of the licensing of SQL Server.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
June 4, 2013 at 7:41 am
Thanks for your feedback. Well it's good to see that my assumptions were right.
I think we have a license for System Center Orchestrator which can handle the scheduling. But I also want to test if we can just install a standard edition for scheduling and still use the enterprise SSIS executables. Otherwise the addional license will be very costly just for scheduling jobs.
__________________
MS-SQL / SSIS / SSRS junkie
Visit my blog at dba60k.net
June 4, 2013 at 10:51 am
Actually, it should have cost you additional licensing to install SSIS on a separate server. The licensing for SQL Server does not allow installing different components on different servers using the same license.
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply