Benchmarking datasets
=====================

When you provision a Lakehouse node, it comes preconfigured to point to
a public S3 bucket in AWS us-east-1 that contains sample benchmarking
datasets.

..  note::
   Accessing these datasets can incur costs for data transfer and be subject to cross-region latencies.

You can query tables in these datasets by referencing them with their
schema name.

.. csv-table::
  :header: Schema name,Dataset
  :widths: 10,30
  :align: left
  :class: longtable

  `tpcds_sf_1`,"TPC-DS, Scale Factor 1"
  `tpcds_sf_10`,"TPC-DS, Scale Factor 10"
  `tpcds_sf_100`,"TPC-DS, Scale Factor 100"
  `tpcds_sf_1000`,"TPC-DS, Scale Factor 1000"
  `tpch_sf_1`,"TPC-H, Scale Factor 1"
  `tpch_sf_10`,"TPC-H, Scale Factor 10"
  `tpch_sf_100`,"TPC-H, Scale Factor 100"
  `tpch_sf_1000`,"TPC-H, Scale Factor 1000"
  `clickbench`,"ClickBench, 100 million rows"
  `brc_1b`,Billion row challenge

!!!note “Notes about ClickBench data”

Data columns (``EventData`` ) are integers, not dates.

You must quote ClickBench column names because they contain uppercase
letters, but unquoted identifiers in Postgres are case-insensitive. For
example:

✅ ``select "Title" from clickbench.hits;``

🚫 ``select Title from clickbench.hits;`` !!!
