August 9, 2010 at 8:17 am
Hi all,
can someone provide me some advantages and disadvantages of using SQL JOBS.
And one of my Job Question is...
Difference between SQL Jobs and SSIS?
Thanks
August 9, 2010 at 8:21 am
You can't compare SQL Jobs to SSIS, they are two different products
You use SQL Agent to run Jobs that can include SSIS packages.
SQL agent and jobs are essential for Sql server as they enable autmoated processes such as backups to occur
August 9, 2010 at 8:46 am
You could think of a sql job as similar to a windows scheduled task and an SSIS package as the task that is scheduled.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
August 10, 2010 at 8:29 am
The others have covered the differences of these two tools.
Why use a SQL Job? One big reason is to run a process at a set time on a regular schedule. It helps you to automate processes.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 11, 2010 at 11:58 am
SQL Jobs, at least in 2000, and very likely in 2005/8, can easily fail or hang without retry or notification.
SQL Jobs are a very useful way of automating work, but if you really, really need to know if a job runs every time, a human checking the job's status and history and perhaps running a check on the results is required. SQL Jobs is not a mainframe-solid scheduling solution.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply