Post reply

Whats the difference between jobs and maintenance plan??

  • February 27, 2012 at 2:16 am

    #256432

    can anyone give me the clear diffrence bw both..

    and

    when u automate a backup strategy which one u choose in ur organization, and why??

    thanks

  • February 27, 2012 at 4:14 am

    #1451973

    satishm94 (2/27/2012)

    can anyone give me the clear diffrence bw both..

    and

    when u automate a backup strategy which one u choose in ur organization, and why??

    thanks

    Maintenance Plans: SQL Server provides you various built-in plans for daily maintenance activities such as backup, re-indexing. As the name suggests Maintenance Plans are specifically used for maintenance only. If you use built-in Maintenance Plans, then you don't need to write any script to perform these maintenance tasks.

    Jobs: Whenever you need to schedule any script/task in SQL Server so that it runs at the specified time or regular intervals, you can do that using SQL Agent Jobs. These jobs are configurable & you can edit the schedule timings, steps that are executed etc. as per your requirement. Maintenance Plans are also scheduled via jobs only.

    What will I choose?: I prefer my own written script but I am not against using Maintenance Plans.

    Sujeet Singh

  • February 27, 2012 at 5:48 am

    #1452006

    Backup strategy.

    http://www.sqlservercentral.com/blogs/glennberry/2010/03/25/recovery-models-and-backup-strategies-for-sql-server-2008/

    java

  • February 28, 2012 at 7:05 am

    #1452571

    For Backups I tend to use maintenance plans.

    For Index and Statistics maintenance, I tend to use scripts. Mostly because Microsoft's Index Maintenance takss don't take into account the level of index fragmentation when they run, so they run for every single index in a database.

    That said, to kick off my scripts, I use an execute SQL task in a Maintenance Plan. It makes finding everything a bit easier.


    --Mark Tassin
    MCITP - SQL Server DBA
    Proud member of the Anti-RBAR alliance.
    For help with Performance click this link[/url]
    For tips on how to post your problems[/url]

  • February 28, 2012 at 8:04 am

    #1452617

    satishm94 (2/27/2012)

    when u automate a backup strategy which one u choose in ur organization, and why??

    I don't automate backup strategies. I automate backups for a recovery strategy. And which one I use depends on which customer I am implementing it for.

    First, create your recovery strategy and SLA on paper. Then design the backups, backup types, and database recovery models based on that.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • February 28, 2012 at 9:46 am

    #1452702

    Brandie Tarvin (2/28/2012)

    First, create your recovery strategy and SLA on paper. Then design the backups, backup types, and database recovery models based on that.

    Exactly what Brandie wrote.

  • February 28, 2012 at 11:08 pm

    #1452921

    Left over interview question.

    http://www.sqlservercentral.com/Forums/Topic1258844-146-1.aspx

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply