May 23, 2012 at 1:59 pm
I wanted to use SQL Server Agent for shcduling the windows jobs as i think sql jobs more robust than windows schduler, do i have install the complete server with a license for this or is it possible tot get just the agent?
May 23, 2012 at 2:20 pm
Tara-1044200 (5/23/2012)
I wanted to use SQL Server Agent for shcduling the windows jobs as i think sql jobs more robust than windows schduler, do i have install the complete server with a license for this or is it possible tot get just the agent?
You need at least standard edition to get the SQL Agent, and yes it requires the full server (it depends on MSDB for a bunch of things). However, agent doesn't take up much overhead, and you could get away with licensing a single-cpu machine.
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
May 23, 2012 at 2:40 pm
would there be any difference in SQL Agent 2005 and 2000?
May 23, 2012 at 3:03 pm
Sorry to say that, but I don't think you should be using SQL Server Agent as a job scheduler if you don't need SQL Server in the first place.
There are lots of job scheduling softwares around that would do it better and with lower costs. Some of them are free and open source.
See here for more details:
http://en.wikipedia.org/wiki/List_of_job_scheduler_software
-- Gianluca Sartori
May 23, 2012 at 3:09 pm
Gianluca Sartori (5/23/2012)
Sorry to say that, but I don't think you should be using SQL Server Agent as a job scheduler if you don't need SQL Server in the first place.There are lots of job scheduling softwares around that would do it better and with lower costs. Some of them are free and open source.
See here for more details:
Gianluca, there's a lot of places I knew that used SQL Server purely for DTS. Now, that meant we just got the SQL Agent for ease of use, but yeah, I know what you're getting at.
OP: If you're getting a new server installed, you'll want to be getting SQL 2k8 R2. Anything else is outdated and not your best choice. As to your question of differences between 2k and 2k5, there's a few thousand differences. The Agent itself isn't that different but what it can do is hugely different. I'd still go to 2k8R2 instead of even caring about the earlier versions if you're simply licensing an Agent server.
However, all that said... I agree with Gianluca. If you just need a scheduler, there's cheaper and better, having been designed to simply BE a scheduler rather then an incorporated element to 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
May 24, 2012 at 3:47 am
There's a task scheduler built right into the OS. I'd just use that utility if all you needed was the ability to schedule tasks. You would have to pay for a license of SQL Server if this was on a production system. That's some serious money just to schedule tasks.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 25, 2012 at 4:46 am
He did say he felt SQL Agent is more robust than Windows task scheduler, but it would be interesting to know why he feels that...I've rarely run into issues with the Windows scheduler.
May 25, 2012 at 5:31 am
paul.knibbs (5/25/2012)
He did say he felt SQL Agent is more robust than Windows task scheduler, but it would be interesting to know why he feels that...I've rarely run into issues with the Windows scheduler.
No doubt SQL Agent allows more flexible schedules, logging and alerting. Windows scheduler lacks many of those features.
However, buying SQL Server just for the Agent looks like buying a house just to park the car in the garage.
-- Gianluca Sartori
May 25, 2012 at 5:52 am
Gianluca Sartori (5/25/2012)
paul.knibbs (5/25/2012)
He did say he felt SQL Agent is more robust than Windows task scheduler, but it would be interesting to know why he feels that...I've rarely run into issues with the Windows scheduler.No doubt SQL Agent allows more flexible schedules, logging and alerting. Windows scheduler lacks many of those features.
However, buying SQL Server just for the Agent looks like buying a house just to park the car in the garage.
Agreed. And, there are 3rd party scheduling products that are more flexible than SQL Agent and probably cost a heck of a lot less than SQL Server.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 28, 2012 at 7:53 am
I'm guessing there are better tool in other infrastructure tools such as System Center
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply