Home
Introduction
The 1010data Macro Language is the most powerful and direct way to interact with 1010data's platform.
Query optimization
Often there is more than one solution to a single problem, and depending on the problem and the data, different approaches can produce better performance. It is important to understand what impacts query performance and how to translate that into optimizing your own queries.
Links
You can use <link> operations in 1010data to combine and filter data between tables. However, depending on the type of link and size of your data, this operation can be costly. It is important to know what steps can be taken while using <link> to optimize your query performance.

Introduction
The 1010data Macro Language is the most powerful and direct way to interact with 1010data's platform.
- What is in a recipe?
  Each recipe in this Cookbook, with the exception of the Debugging Guide, contains the same basic elements. This page describes the contents of each section contained in a recipe and the elements that make a Debugging Recipe different.
- Difficulty criteria
  Each recipe is equipped with a difficulty measure based on the criteria discussed in this section. A recipe holding a specific difficulty rating can contain one more of the elements in the description of that level or a lower level.
- Query optimization
  Often there is more than one solution to a single problem, and depending on the problem and the data, different approaches can produce better performance. It is important to understand what impacts query performance and how to translate that into optimizing your own queries.
  - Lazy evaluation
    Certain operations in 1010data are not evaluated until the data from those operations are needed by another part of the query.
  - Selections
    The order in which selections are made and the method in which selections are made can affect the efficiency of your query.
  - Links
    You can use <link> operations in 1010data to combine and filter data between tables. However, depending on the type of link and size of your data, this operation can be costly. It is important to know what steps can be taken while using <link> to optimize your query performance.
    - Tables vs. worksheets
      When you perform one or more operations on a table, it becomes a worksheet. It is important to understand the differences and implications of linking to a worksheet rather than a table.
    - Prelinks
      You can save time when linking two tables where a prelink exists because the <link> is already evaluated.
    - Segby links
      Linking on a column that your foreign table is both sorted and segmented by (i.e., sortseg), can make your <link> more efficient.

Links

You can use <link> operations in 1010data to combine and filter data between tables. However, depending on the type of link and size of your data, this operation can be costly. It is important to know what steps can be taken while using <link> to optimize your query performance.

Although there are steps you can take to improve performance while using a <link> operation, sometimes links can be avoided entirely by denormalizing your tables. For example, if you have a group of retail tables, including a sales history table, a store master, a product master, and a customer master, any time you need further information other than what is included in the sales history table, you have to link in one of the master tables. However, if all of these individual tables were denormalized to create one large table, you would always have all of the information you need without linking. It is important to consider your data and the types of queries you expect to perform before making a decision on whether to denormalize or simply use <link> operations to combine tables.