Next in our series of Faststats blogs: 5 things you need to know about FastStats Designer

5 things you need to know about FastStats Designer

Screenshot of Faststats Designer table relationships
Screenshot of Faststats Designer table relationships
  1. Build speeds increase rapidly with the right hardware configuration – allow at least 4 times the size of your underlying data (as measured by the size of the combined text files within the ‘extract’ node), use fast processors (especially Intel, which tests have proved significantly out-perform AMD chips for FastStats builds) and turn off balanced power settings and instead use High Performance
  2. Point your Dev, UAT and Live versions of the Build to different folder locations – use Environmental User Defined Variables to simplify this process, and schedule Batch Files to refresh each type or your Build(s) as desired
  3. Logs, logs, logs.  There are plenty of them for you to check and keep on top of.  They’re there to help you after all!  The Build_Log.txt, which you can find in the Build directory for your system is a great place to start
  4. Designer now allows you to create composite keys.  Apply the composite key in the Design saves bringing in extra/unnecessary fields. Less data = quicker build
  5. Let the Design take the strain… Avoid allocating specific datatypes to every field in your new/existing Build. Leave (or [re]set) the datatype to the default type of Selector/0 to trigger the Build to allocate the appropriate datatype.
Skip to content