I was a little surprised today when another DBA did not know the effect of using a VARCHAR2 datatype for what is functionally a number.\u00a0 I wanted to ensure I had an article to which I could point when this question comes up in the future, so here it is. <\/p>\n
A VARCHAR2 that functions as a number will not be very usable for what would normally result in a range scan execution plan. If you think about it, this makes sense. You can intuitively look at all values (regardless of “datatype”) between 10 and 900 and say there are 890 values between the two. If however, you are a computer, you will sort it as though 10 is a alphabetic character, and 900 is an alphabetic character, since that is what the data is. In other words, 1,000,000,000,000 is less than 2, since the leading 1 is less than 2. <\/p>\n
Below shows a test case and the optimizer execution plan for each.<\/p>\n
\r\nSQL> create table vchar(c varchar2(20));\r\n\r\nTable created.\r\n\r\nSQL> create table num(c number);\r\n\r\nTable created.\r\n\r\nSQL> begin\r\n 2 for i in 1..100000 loop\r\n 3 insert into vchar values(i);\r\n 4 insert into num values(i);\r\n 5 end loop;\r\n 6 end;\r\n 7 \/\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSQL> create index vchar_i on vchar(c);\r\n\r\nIndex created.\r\n\r\nSQL> create index num_i on num(c);\r\n\r\nIndex created.\r\n\r\nSQL> exec dbms_stats.gather_table_stats(USER,'VCHAR');\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSQL> exec dbms_stats.gather_table_stats(USER,'NUM');\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSQL> explain plan for select * from vchar where c between '10' and '900';\r\n\r\nExplained.\r\n\r\nSQL> select * from table(dbms_xplan.display());\r\n\r\nPLAN_TABLE_OUTPUT\r\n-----------------------------------------------------------------------------------------------------------------\r\nPlan hash value: 600218931\r\n--------------------------------------------------------------------------------\r\n| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |\r\n--------------------------------------------------------------------------------\r\n| 0 | SELECT STATEMENT | | 88900 | 434K| 45 (5)| 00:00:01 |\r\n|* 1 | INDEX FAST FULL SCAN| VCHAR_I | 88900 | 434K| 45 (5)| 00:00:01 |\r\n--------------------------------------------------------------------------------\r\n\r\nPredicate Information (identified by operation id):\r\n---------------------------------------------------\r\n\r\n 1 - filter(\"C\"<='900' AND \"C\">='10')\r\n\r\n13 rows selected.\r\n\r\nSQL> explain plan for select * from num where c between 10 and 900;\r\n\r\nExplained.\r\n\r\nSQL> select * from table(dbms_xplan.display());\r\n\r\nPLAN_TABLE_OUTPUT\r\n-------------------------------------------------------------------------------------------------------------\r\nPlan hash value: 3771115364\r\n--------------------------------------------------------------------------\r\n| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |\r\n--------------------------------------------------------------------------\r\n| 0 | SELECT STATEMENT | | 892 | 3568 | 3 (0)| 00:00:01 |\r\n|* 1 | INDEX RANGE SCAN| NUM_I | 892 | 3568 | 3 (0)| 00:00:01 |\r\n--------------------------------------------------------------------------\r\n\r\nPredicate Information (identified by operation id):\r\n----------------------------------------------------\r\n 1 - access(\"C\">=10 AND \"C\"<=900)\r\n\r\n13 rows selected.\r\n\r\nSQL>\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"I was a little surprised today when another DBA did not know the effect of using a VARCHAR2 datatype for what is functionally a number.\u00a0 I wanted to ensure I had an article to which I could point when this…<\/p>\n