Re: Optimize - Using Temp, Using Filesort, Group By Having
Posted by:
Lenny Dunn
Date: April 19, 2011 12:18PM
Yes, I will be removing the redundant 'complete' key.
The 'tracking_number' key was assigned VARCHAR due to the data being alphanumeric with some symbols. Now for the size, that was just a default I selected but it can realistically be reduced to 75. UTF8 was chosen to keep everything standard across the databases, web applications and PC/Mobile applications. After doing more reading, I assume you posed this question because of the single byte vs. multi byte causing an increase in size? You have stumped me on the surrogate key question. Maybe due to my lack of understanding, I do not know where or how this could assist.
Looked at reference and will be making some tweaks.
After seeing what a difference being exact on data types can do for indexes, I will be reviewing and adjusting the data type database wide.
Thank you.
Subject
Views
Written By
Posted
5677
April 08, 2011 10:40AM
2124
April 09, 2011 11:37PM
1643
April 12, 2011 01:38PM
2298
April 13, 2011 07:56AM
1642
April 13, 2011 09:44AM
2188
April 14, 2011 12:08AM
Re: Optimize - Using Temp, Using Filesort, Group By Having
2225
April 19, 2011 12:18PM
1634
April 19, 2011 10:40PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.