Updating tinyint columns in oracle
In the next section, we dissect Ola’s script so that we better understand how it works.
At the same time, we will learn how it can be customized for your specific environment.
While it is possible to create a decent database maintenance plan using the Maintenance Plan Wizard (see my free e Book: Brad’s Sure Guide to SQL Server Maintenance Plans), the tool is not very flexible, and if it isn’t properly used, it can result in poor database maintenance.
Another common way for more experienced DBAs to create database maintenance plans is to create custom T-SQL or Power Shell scripts to perform database maintenance.
The second option is used to tell the script if you want it to automatically create SQL Server Agent jobs for you that are pre-configured, and ready to run, although they still need to be scheduled. If you don’t want the script to automatically create the jobs for you, then replace ‘Y’ with ‘N’.
If implemented correctly, a database maintenance plan can help ensure that a SQL Server’s databases perform optimally and, if there should be a problem, provide the necessary backups to minimize the loss of any data.
Another benefit of implementing a database maintenance plan is that it helps to prevent, or at least to catch early, many different kinds of database-related problems.
Ola Hallengren is a DBA and database developer who is currently working with a large financial company in Sweden. Back in 2007, Ola began a project to improve the database maintenance within a large SQL Server environment.
At that time, a combination of database maintenance jobs created using the SQL Server Maintenance Wizard, along with a collection of custom Transact-SQL scripts, were used throughout the organization.By being proactive with a good maintenance plan, time spent troubleshooting problems after the fact is often reduced.