We have a bit of a debate going on in the office right now and will be very grateful for peoples feedback.

We are currently planning a new application and want to make sure we can upsize to SQL in the future, this is our first attempt at an upsizable application.

As a result we are considering attempting to access all tables through views.

1. Should application specific tables such as our application registry be also be a view. Does this degrade performance.


2. Is it overkill planning to treat our small lookup tables as views.


3. Certain views we create will mean recreating indexes for them at system start time. How big should these views be before its worth while bothering with an index. (I know Rushmore will create one when necessary)


Thanks