Databases Reference
In-Depth Information
is determining whether the tasks should be performed manually or should be
automated.
Manual tasks
are tasks that require operator intervention. In order
words, you must initiate the task each time it is performed.
Automated tasks
run without direct operator intervention, either on a periodic basis or in response
to an alert or other triggering event.
Additionally, there is the issue of what utilities to use. Often, you have the choice
of using either a command-line interface or graphical interface utility. Sometimes,
the choice is simply one of personal preference, but there can be important differ-
ences. The functionality and specific features supported can sometimes vary between
graphical-user-interface (GUI)-based and command-line utilities, with the com-
mand-line utility usually being the more powerful of the two. It may be an issue
of automation, because some GUI-based utilities aren't designed for automated use.
Picking the Right Utility
When deciding what utility to use to perform a task, you must consider several
factors, including the following:
▲
Available Utilities:
sometimes, there's only one way to perform a task,
so the decision is made for you.
▲
Functionality:
you must determine which utility is able to perform all
of the aspects of the task that you require.
▲
Reporting Options:
there is often an issue, especially during performance
monitoring and troubleshooting, of how much information is provided
by the utility and in what form.
▲
Interaction and Conflict:
some utilities have a more pronounced impact
on database performance while running, meaning that you might want to
either use an alternate utility or run the procedure after hours (hopefully
as an automated process).
In all cases, pick the tool or utility that is able to complete the task you need
done. Take SQL Server for example. You can perform some common tasks, like
backup and restore, using either a command-line command or SQL Server Man-
agement Studio. Other tasks, such as setting up a data protection mechanism
known as database mirroring, are supported through command-line utilities only,
so there's no choice to make.
After considering your requirements, if you still have multiple options avail-
able, and other factors are more-or-less equally balanced, consider ease of use.
There is no reason to make your job more difficult than necessary. Consider,
again, running a data backup. Most database administrators find it easier to use
SQL Server Management Studio to set up backups, especially when different
types of backups running under different schedules must be included, because
of the graphical scheduling interface.
