In order to start optimizing this query, we must go through what I have called previously initial considerations of query optimization. For the sake of this example, let's say that this table will be the object of READ queries more than WRITE queries because the data will remain fairly static once written to the table. Also, it is important to note that creating an index on the first_name column of the actor table will make the index prone to generating equivocity due to non-unique values in this column. Moreover, let's say that scalability is important because we intend on having many users querying this table every hour and that the table size should remain manageable on a long-term period.
This being given and ...
