You can use the attached dbf table as a join to your date field (the field must have dates only with no time other than 12 AM) to associate all of the typical date component groupings and break-downs, without calculating those values into the feature class or creating separate layers for each date grouping. The table covers all dates between 1/1/1860 and 1/1/2102. All grouping fields are numeric and are:
YEAR_VALUE (only the values 1860-2102)
MONTH_VALU (only the values 1-12)
YEAR_MONTH (values 186001 to 210201, with the first 4 digits being 1860 to 2102 and last two digits being between 01 and 12)
YEAR_DECIM = YEAR_DECIMAL_MONTH in gdb (a numeric representation of the year with a fractional value for the month of the year in 1/12th fractions)
YEAR_DEC_1 = YEAR_DECIMAL_DAY in gdb (a numeric representation of the year with a fractional value for the day of the year in 1/365th or 1/366th fractions)
DAY_VALUE (only the values 1-31)
Because all of the grouping fields are numeric you can construct Quantities or Charts symbology with these values. You can also do a multi-field sort of your table view by the MONTH_VALU field and then the YEAR_VALUE field or by the DAY_VALUE before or after the MONTH_VALU or YEAR_VALUE with this table joined to your date field. Of course, if you join the table and then export/ copy features, etc. you can permanently add all of the grouping fields to a copy of your feature class without doing multiple field calculations.
If you feel the table should include other grouping fields let me know. For example, a string version of the Month and Day fields with leading zeros could be useful for Category symbology so that it sorts correctly, or a set of quarter or fiscal year groupings (for example, numeric fractional fiscal years like 20142015 with July 1-31 set as a fractional value of 0 and June 1-30 is set as 11/12th of the year for sorting purposes)