I recently had a discussion with someone who said that using a view on a database with a large number of tables and (>1,000000) rows would allow for much better performance.
I don't see how this would be the case as a view is just a stored query definition as far as I am aware.
This was in relation to a web based app which allows for the filtering of products based on type, brand, spec, etc... and needs to be very performant.
Given that queries are effectively hard coded into the app, its not like a person needs to create each query manually so I'm thinking that there should be no difference between using a view or running a standard query againts the needed tables that uses joins...
I had suggested that using indexes on the tables would allow for the performance needed but they said that when tables have more than around 200k rows, indexes are useless in terms of speeding things up...
Is this correct about table size removing the effectiveness of indexes and are there any performance increases to be had from using views over standard queries?
Any help will be much appreciated.