Is it better to have a view created or to perform a full select clause in terms of speed

Question

0.00/5 (No votes)

See more:

I'm working on a summary (some sort of simple reporting of data) to help me explain my customers how much time I've spent in the different parts of the projects I work in.

I need to be able to filter the existing data, to show the amount of hours of each kind I've worked in each week/month/year while the project was on...

I've thought of a big (for me that I'm not used to it +/- 80 lines) SQL clause that prepares all the data, but then I'm having problems to filter it at will, so I've thought of creating a view using that SQL clause and then filter it afterwards.

And then the other question appeared... is it faster to have views ready or making the query every time?

What I have tried:

Nothing, just asking for some information...

Posted 21-Jun-20 12:51pm

Joan M

Updated 21-Jun-20 16:34pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Afzaal Ahmad Zeeshan · Accepted Answer · 2020-06-21T16:35:00

Short: A View can cache the results if you apply an index for future queries which leads to improved performance for subsequent requests. Otherwise, a View is just an alias for regular-SQL query.

Check out these posts to understand why a View is faster than a plain-SQL query:
sql - Is a view faster than a simple query? - Stack Overflow[^]
database - Performance of VIEW vs. SQL statement - Stack Overflow[^]
indexing - How do I get MySQL to use an INDEX for view query? - Stack Overflow[^] (definitely read this one!)

It all boils down to whether the View you are creating/using/executing is being indexed or not. If you are not using any indexes, and are plain-old-executing the query, then a View is likely to be an alias for the SQL query, only. The performance part comes, when you handle the indexes on the view and let MySQL reuse the results from previous queries.