Installing the "Ola Scripts" for SQL Server

A quick demo of how to install scripts from ola.hallengren.com on SQL Server for easy maintenance of your systems.
After the intro, if you are not interested in watching a SQL install ...skip to 5:03 for the beginning of the Ola specific part
Also...Ola created job are NOT scheduled by default...you have to do that based on your maintenance windows and environment.
More DBA Fundamentals at: www.dallasdbas....

[@Siege2Sage]

Oh my God, I was scratching my head for the past twenty minutes trying to figure out how these scripts work. Thank you for that lovely explanation. I feel more confident now using OLA scripts for my enterprise database :)

[@Kevin3NF]

Glad it helped!

[@jimz6076]

For companies that have small budgets, for managers that need to get people trained with no training budget, and those of us that have no formal DBA training that learn from hands on experience we all Thank you and Ola.

[@Kevin3NF]

You just made my day kind sir! Feel free to request a "basics" video and I'll see what I can do. Ideally something that affects lots of people, or a concept that needs to be explained in less "DBA" language.

[@lio83210]

Thank you Kevin Hill, Jim said it all. We often have no training and you are the source of explaining what we should do next with Ola's script. Thanks to both of you !

[@dcbc991]

Thanks Kevin for putting this together. Very straightforward and loaded with value.

[@michaelashe107]

Thanks! been looking at the scrips and figuring out how to get started. This does help a bunch!

[@oysteinkleppestrand6375]

Excellent guide to help me getting started with the scripts! Thanks.

[@WillB0212]

Things to note... the job setup is cool (I also use Ola). I recommend changing the way the job reads its parameters to using powershell and running the stored procedures inside the DBAdmin database (because that's all this really is is a lovely script of sprocs). You can also develop to set retention time from hours to days if you'd prefer. This works best for keeping 0 retention. If you ever have any Ola questions, feel free to ask.

[@Kevin3NF]

Thanks William...but lets remember this is a beginner level video to get folks started that may not be DBAs.

[@WillB0212]

@@Kevin3NF For sure! I'm just throwing out next level ideas; and offering any help if needed. :)

[@TheSerialKiller131]

if i need to go and change the ola file, where i can find it?

[@Kevin3NF]

If you mean the stored procedures that run the backups, index maintenance, etc. they are installed in whatever database you specify when you run the MaintenanceSolution.sql file. by default, that is master...but please make a different DB for this.

[@skatterbrainz]

Very nice! Would you consider a follow-on about creating a maintenance plan to chain multiple (Ola) agent jobs in a recommended sequence?

[@WillB0212]

Like, running your indexing ola jobs after your backup ola jobs? You could chain it I suppose. Chaining can be bad if there's a failure in between (though you could code past that). I'd really recommend just sticking to some schedule. Just my two cents.

[@harshthakkar8703]

Hi
Could we check the output of database integrity for user databases in log file. For ex: dbcc checkdb output

[@Kevin3NF]

Ola scripts create their own log files when they run...easiest is to check that. If there is corruption reported, the job will show as failed. You should be alerting on failed jobs, so you will know right away. Also turn on alerts for errors 823/824/825

[@purnachandra1757]

How to set the parameters for these scripts

[@Kevin3NF]

That will depend on your organizational goals, workload performance, etc. Start with the defaults and adjust as needed

[@JKoz-sf2ei]

awesome information!

[@ragespawn8043]

How can you specify which database will be affected by the script and where do you specify it ?

[@Kevin3NF]

Each job takes a database parameter, where you can specify a group such as "all_databases", or in groups. Check this link from Ola: ola.hallengren.com/sql-server-backup.html

[@WillB0212]

You have a 'USER_DATABASES', 'SYSTEM_DATABASES', and then you can actually specify specific databases instead 'DB_1, DB_2, DB_4'. You can even exclude (say you want all user databases but DB_3) '-DB_3'.

[@freakytej8357]

Hi ,
I wanted to exclude particular 'X' database how can I find 'DB_1' ,is my particular database relates ?Please help me out..

[@mm-ic1xs]

very good!

[@BradSmithSC]

Subscribed

[@WillB0212]

Dude... automate that SQL Server Installation with Powershell. Come on! ;)