Sorry for the long question, but let me give you my scenario. I have a DB that houses data exported from another DB. The containing tables are copies from the other (non-SQL) database. Each column name in these export tables is named using the following pattern:
Since our user's are primarily interested in the UserFriendlyName portion of the column, we have created a View for each table, where the name of each field is strictly the UserFriendlyName portion of the column name.
Most of these Views are strictly queries of one data table. For some of these views, however, I link to one other data table to pull out a description field or two. Note, this is never more than one linked table.
Performance wise, which method if better? If I am linking one data table to another for a description field, can I link straight to the description tables View so that I don't have to alias the column? Is it significantly better to use two data tables in the View and alias each column from the parent tables?
This may seem a bit arbitrary but this data exportation project is getting bigger and bigger. I'd like to formalize my process in how I link my information together. The goal is to strictly use the Data Views if and when possible. However, if this adds a sizable amount of performance degradation, I'd rather stick with always using Data Tables in all of my Data Views.