Data Movement · Topic 13 of 17

Marketplace, Listings and Auto-Fulfillment

Share data through the Snowflake Marketplace and listings, and manage cross cloud auto-fulfillment: refresh options, size limit and requirements.

  • 4 min
In a nutshell
  • A listing wraps a share or application package with metadata, and can be public (Marketplace) or private.
  • Cross cloud auto-fulfillment replicates a listing's data product to other regions and clouds, managed by Snowflake.
  • Refresh types: trigger (SYSTEM$TRIGGER_LISTING_REFRESH), interval (1 minute to 8 days), schedule.

What it is

A listing is the packaged offer of a data product: a share or an application package, plus a title, description, sample queries and terms. The Snowflake Marketplace is the public place where providers publish listings for any Snowflake customer to find. A private listing goes to named accounts only. Auto-fulfillment replicates the data product to other regions and clouds so that consumers anywhere can use it.

Providerbuilds listingpublishesMarketplace or private listingconsumer clicks GetConsumerdatabase createdqueriesShared dataListingin region Aauto fulfillmentReplicain region BservesConsumer in region B

How it works

Marketplace and private listings

Marketplace listingPrivate listing
AudiencePublic, discoverable by any accountSpecific accounts you name
PricingFree, limited trial or paidSet by the provider, can be free
Typical useSelling or giving away datasets and appsSharing with partners, customers or other accounts you own
Cross region deliveryAuto-fulfillment (manual replication allowed for free or limited trial listings)Auto-fulfillment, detected automatically

A provider prepares a listing in Snowsight, selects the share or application package, adds the description, sample SQL and documentation, and publishes it. A consumer finds a Marketplace listing, accepts the terms and chooses Get, which creates a read only database. Some listings let the consumer request the data first, and the provider approves.

Compared with a plain share, a listing adds discovery, metadata, usage analytics for the provider, paid and trial options, and cross region delivery. A direct share works only inside one region on one cloud.

Exam tip

If a scenario needs data delivered to consumers in different regions or clouds, the answer is a listing with cross cloud auto-fulfillment, not a direct share.

How auto-fulfillment works

Snowflake manages a secure share area in each commercial region for your organization. When a consumer in a new region gets the listing, Snowflake fulfills the data product to that region. If the product is already there, the consumer gets it immediately.

  • Private listings: fulfilled after the specified consumers get the listing.
  • Public Marketplace listings: fulfilled after a consumer in that region gets the listing.
  • Configuration: you can set auto-fulfillment on a draft or published listing.
Provider listingconsumer in new region gets itSnowflakesecure share areafulfillsRegion copyrefreshes onSchedule or trigger

Refresh options

Refresh typeHow it works
Trigger basedRun a refresh on demand with SYSTEM$TRIGGER_LISTING_REFRESH
Interval basedRefresh every 1 minute up to 8 days
Schedule basedRefresh at a set time and schedule

Interval and schedule settings cannot be used together. For shares the refresh applies per database, and for application packages it applies to the account.

Requirements, limits and monitoring

  • A full account is needed. Trial accounts cannot use auto-fulfillment.
  • Accounts that signed up through the AWS, Google Cloud or Azure marketplace can only fulfill within that cloud.
  • Auto-fulfillment adds cost, and larger data products cost more. The initial refresh has a default 10 TB limit, which an account administrator can raise with the LISTING_AUTO_FULFILLMENT_INITIAL_REFRESH_SIZE_LIMIT_IN_TB parameter after weighing the cost.
  • Government and VPS regions get their own secure share areas, so data stays inside that environment.
  • Snowflake emails a daily summary of failed refreshes to the listing contact, and LISTING_REFRESH_HISTORY returns 14 days of refresh history per target region.
  • Paid Marketplace listings use auto-fulfillment, and private listings cannot be manually replicated.
Watch out

Fulfilling a large product into many regions multiplies the cost. Set a sensible refresh interval, because a one minute interval on a big data product increases refresh work.

Consumer side

The consumer gets a database from the listing, grants imported privileges to local roles and queries the data. As with shares, the consumer pays for compute and the data is read only. If the listing is an application package, the consumer installs a Native App instead.

Common mistakes

  • Using a direct share to reach consumers in another region or cloud.
  • Setting both an interval and a schedule and expecting both to run. One overrides the other.
  • Publishing a very large data product without checking the 10 TB initial refresh limit.
  • Expecting a trial account to use auto-fulfillment.
  • Assuming a Marketplace listing is only for free data. Paid and limited trial listings exist.
  • Forgetting that private listings are for named accounts, while Marketplace listings are public.

What to remember for the exam

  • A listing wraps a share or application package with metadata, and can be public (Marketplace) or private.
  • Cross cloud auto-fulfillment replicates a listing's data product to other regions and clouds, managed by Snowflake.
  • Refresh types: trigger (SYSTEM$TRIGGER_LISTING_REFRESH), interval (1 minute to 8 days), schedule.
  • Default initial refresh size limit is 10 TB, raised with an account parameter.
  • Not available on trial accounts. Extra cost for each region.
  • LISTING_REFRESH_HISTORY holds 14 days of refresh history.
  • Direct shares work only within a region.

Check yourself

  • A provider wants to sell a dataset to customers on different clouds. What should it publish?

    A paid Marketplace listing, which uses cross cloud auto-fulfillment to serve other regions and clouds.

  • How can a provider force a fulfilled listing to refresh right now?

    Call SYSTEM$TRIGGER_LISTING_REFRESH.

  • Which view shows the refresh history of a listing per region, and for how long?

    LISTING_REFRESH_HISTORY, with 14 days of history.

Topic 13 of 17 in Data Movement

Test yourself on Data Movement

The full Snowflake DEA-C02 question bank has 709 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.