Forum Discussion

Grumelo's avatar
Grumelo
Advocate II
5 years ago

Too Many Date Tables

My data model is very huge. There are plenty of date fields.

Only very few them are used in various report and agregations. (edit: for these fields the automated date table is perfect).

Is there a way to not generate an automated date table for every single date field?

I don't need the date hierarchy on most of them. 

 

I don't want to globally turn off the automated date table feature. I 'd like to turn it off on some fields only.

 

All these automated date tables seem to impact performance and memory usage.

 

Until now the only solution I've found is to not set the field as date field but then I've to carefully set the format of the field in the queries.

Any better trick ?

5 Replies

    • Grumelo's avatar
      Grumelo
      Advocate II

      I was maybe not clear enough.

      I don't want to to turn the automated date table off on every date fields, only on some of them.

      • FrankAT's avatar
        FrankAT
        Community Champion

        Hi Grumelo 

        a well formed data model needs only one calendar table. This calendar table should be marked as date table so all time and date intelligence functions works well. It is best practice to uncheck the automatic date table functionality as Greg_Deckler described.

        If you need in some circumstances, build your own date hierarchy manually. A mixture of automatic date tables and a calendar table is not recommended.

         

        With kind regards from the town where the legend of the 'Pied Piper of Hamelin' is at home
        FrankAT (Proud to be a Datanaut)