Why Is My Query Slow? More Reasons Storing Dates as Numbers Is Bad

Storing dates as numbers can cause unexpected problems.

In this video Chris looks at one possible issue: inconsistent query performance.

He then shows methods you can use to improve performance, including function-based indexes and histograms.

============================
The Magic of SQL with Chris Saxon

Copyright © 2015 Oracle and/or its affiliates. Oracle is a registered trademark of Oracle and/or its affiliates. All rights reserved. Other names may be registered trademarks of their respective owners. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the “Materials”). The Materials are provided “as is” without any warranty of any kind, either express or implied, including without limitation warranties or merchantability, fitness for a particular purpose, and non-infringement.

[xnbet]

Great video about storing a date as a date.

[mariuszzacharuk]

If you don't need HH:MI:SS data, you can store data in a Julian format (which is just an number) and it will be completely fine

[royniemann]

Your videos have generally been excellent but this one puzzles me. Two things: why not convert the fields to dates? I still do not understand why crossing the year confuses the optimizer. What am I missing?

[jbucata]

I noticed you stopped putting the chimes sound effect on the scene transitions... I hope you didn't do that because of my comments on your previous video! I remember when you had the chimes playing constantly whenever you had a superimposed graphic. THAT was distracting.... but conversely this silence between "scenes" feels weird.