I would say it's a different way ;-)
It depends on the data, tables joined, and other things. It may look
and work great in typical emp-dept example: few departments, few
dozens employees. When you use GLOBAL hints you can overwrite
hints used inside the view but I don't think you can change o
There's a better way: use global hints in the queries that select from
the views. From Designing and Tuning for Performance:
Global Hints
Table hints (i.e., hints that specify a table) normally refer to tables
in the DELETE, SELECT, or UPDATE statement in which the hint occurs,
not to tables in
Maria,
Witold has provided some good advice so no need to repeat any of that.
But, since you are asking about hints and views it is worth mentioning the
concept of GLOBAL hints. When you want to specify hints for tables that
appear *inside* views you can use GLOBAL hints. So, you might find this
I had to use hints inside views number of times and it worked well
but you have to be careful. Hinting just the SQL statement that
builds the view may be worse than no hinting at all.
When you add hints you have to keep in mind how you will use the
view. In result I ended up with few views, se
