patternsqlMinor
Deploying Ola Hallengrens scripts - Index Optimization
Viewed 0 times
hallengrensscriptsdeployingoptimizationindexola
Problem
Never before I used Ola Hallengren Scripts .
I am planning to deploy the Ola Hallengren scripts for Index Optimization for the first time. I need to deploy them in PROD so I want to be more careful. Anyhow will first test in Dev environment. But please help me understanding the important things to keep in mind before deploy OH Index optimization scripts.
I copied the media from link and below commands :
As I mentioned I never deployed the OH scripts before.
Can anyone who already deployed and successfully using the OH Index Optimization scripts guide me on below:
NOTE : We are using AOAG 2014.
Please help me keeping this in mind. I can first test in Dev and later deploy in PROD.
I am planning to deploy the Ola Hallengren scripts for Index Optimization for the first time. I need to deploy them in PROD so I want to be more careful. Anyhow will first test in Dev environment. But please help me understanding the important things to keep in mind before deploy OH Index optimization scripts.
I copied the media from link and below commands :
As I mentioned I never deployed the OH scripts before.
Can anyone who already deployed and successfully using the OH Index Optimization scripts guide me on below:
- Important parameter Values which I need to modify?
- Where will these commands create the SP and related Command Execute and Command Log, all in Master Database or MSDB?
- Series of code execution - Which code I need to execute first?
- What is command Log here?
- We are with AOAG set up on SQL Server 2014. Please guide me keep this in view.
NOTE : We are using AOAG 2014.
Please help me keeping this in mind. I can first test in Dev and later deploy in PROD.
Solution
-
The parameters will depend on what tasks you want, how often and when you want to run them. This is really up to you.
-
The default location is master db, you can put them elsewhere. But i dont see much benefit in doing that.
-
Run the script to create the command log table first.
-
The command log table can be used by the scripts to log events.
-
Availability groups are supported.
Most of these questions are answered in Ola's FAQ. I highly reccomend you read it.
Personally, I find the full maintenance solution is too much. I prefer to just call the tasks I want using the examples provided.
But it's worth running it in dev as it will give you working examples of how to create the agent jobs. There is no "right answer" with this stuff, you really need to experiment and select what is right for you.
One thing I struggled with is that if you want to back up to a network address you need to grant permission to the account that SQL Server uses. Therefore it should be a domain account.
The parameters will depend on what tasks you want, how often and when you want to run them. This is really up to you.
-
The default location is master db, you can put them elsewhere. But i dont see much benefit in doing that.
-
Run the script to create the command log table first.
-
The command log table can be used by the scripts to log events.
-
Availability groups are supported.
Most of these questions are answered in Ola's FAQ. I highly reccomend you read it.
Personally, I find the full maintenance solution is too much. I prefer to just call the tasks I want using the examples provided.
But it's worth running it in dev as it will give you working examples of how to create the agent jobs. There is no "right answer" with this stuff, you really need to experiment and select what is right for you.
One thing I struggled with is that if you want to back up to a network address you need to grant permission to the account that SQL Server uses. Therefore it should be a domain account.
Context
StackExchange Database Administrators Q#179942, answer score: 3
Revisions (0)
No revisions yet.