Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sIjTs-0000Ue-JW for pgsql-announce@arkaria.postgresql.org; Sun, 16 Jun 2024 06:35:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sIjTp-003efe-UJ for pgsql-announce@arkaria.postgresql.org; Sun, 16 Jun 2024 06:35:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sIjTp-003efO-2t for pgsql-announce@lists.postgresql.org; Sun, 16 Jun 2024 06:35:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sIjTm-001vNQ-I5 for pgsql-announce@lists.postgresql.org; Sun, 16 Jun 2024 06:35:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=DzxO1Xo0jSltYbCTre6VkZ7Yeh3OQgiqKcLCwKOdZ+4=; b=Rw9H+ZkULeGiVUSc5xkwKXwsMe e3Fjg1M7OTC6KEJo+b+D1lW/VZWI9y1IORTR4Qu/LsWnvI1gggdGBiRkTSypTG+mqr7YjYf/jHcf+ q82ePiJ9tZmyJVc6IpQFbr9hPL8auj0FvOjfGAhaEserD9grZL6J5StseHaYpAa0TjWnvJWSnnS/C VmGhgtYcUREI69UYPzrJ0gZf0X7ICqXx3oPRnMxQFJCcXAf4trwn/qg2Cx43Hdf6MJ7dF0KdUMuN1 JPA5qwK2sgmTkqjSp5c+woNKJPI+SKghYyw8D91IShCl+uhFrd8EMGLt5EkqUpoWipGHh/0iXO/lA 9IaNmy4g==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sIjTl-004x49-10 for pgsql-announce@lists.postgresql.org; Sun, 16 Jun 2024 06:35:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sIjTi-008bOr-0R for pgsql-announce@lists.postgresql.org; Sun, 16 Jun 2024 06:35:02 +0000 Content-Type: multipart/mixed; boundary="===============1155029172584239531==" MIME-Version: 1.0 Subject: Load Data from PostgreSQL to Snowflake Using Estuary Flow To: PostgreSQL Announce From: Estuary Flow via PostgreSQL Announce Reply-To: sourabh@estuary.dev Date: Sun, 16 Jun 2024 06:34:16 +0000 Message-ID: <171851965605.20943.18392572927839209252@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: proprietary X-pglister-tagsig: 4f287bdd2f8075259c56b84c8e21e811c5516566267fba35e73ca80a14447704 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============1155029172584239531== Content-Type: multipart/alternative; boundary="===============2149639645490721527==" MIME-Version: 1.0 --===============2149639645490721527== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable We are happy to share that you can easily load data from Postgres to Snowfl= ake using Estuary. Estuary Flow is a game-changer, offering real-time, reliable change data ca= pture (CDC) and seamless batch data movement in a single pipeline. Whether = you're powering analytics, operations, or AI, Estuary Flow's speed, reliabi= lity, and flexibility are unmatched. ## Load Your Data from Postgres to Snowflake in 8 Simple Steps: 1. Create an Estuary Flow Account: Get started with a free trial. 2. Configure AWS RDS (Postgres): Set up your PostgreSQL database on AWS. 3. Local Postgres Setup: Complete the database configuration locally. 4. Create and Load a Table: Populate your PostgreSQL table with data. 5. Set up Snowflake: Prepare your Snowflake data warehouse. 6. Create a Capture: Tell Estuary Flow which data to capture. 7. Create a Snowflake Materialization: Define where the data should land in= Snowflake. 8. Verify Data Accuracy: Ensure everything is in sync and accurate. For detailed instructions and screenshots at each step, refer to Estuary's = official guide: [Postgres to Snowflake](https://estuary.dev/postgres-to-sno= wflake/) --===============2149639645490721527== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Load Data from PostgreSQL to Snowflake Using Estuary Flow
 

Load Data from PostgreSQL to Snowflake Using Estuary Flow

We are happy to share that you can easily l= oad data from Postgres to Snowflake using Estuary.

Estuary Flow is a game-changer, offering re= al-time, reliable change data capture (CDC) and seamless batch data movemen= t in a single pipeline. Whether you're powering analytics, operations, or A= I, Estuary Flow's speed, reliability, and flexibility are unmatched.

Load Your Data from Postgres to= Snowflake in 8 Simple Steps:

  1. Create an Estua= ry Flow Account: Get started with a free trial.
  2. Configure AWS R= DS (Postgres): Set up your PostgreSQL database on AWS.
  3. Local Postgres = Setup: Complete the database configuration locally.
  4. Create and Load= a Table: Populate your PostgreSQL table with data.
  5. Set up Snowflak= e: Prepare your Snowflake data warehouse.
  6. Create a Captur= e: Tell Estuary Flow which data to capture.
  7. Create a Snowfl= ake Materialization: Define where the data should land in Snowflake.
  8. Verify Data Acc= uracy: Ensure everything is in sync and accurate.

For detailed instructions and screenshots a= t each step, refer to Estuary's official guide: Postgres to Snowflake
This email was sent to you from Estuary Flow. It was delivered on their beh= alf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Estuary Flow.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Proprietary. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============2149639645490721527==-- --===============1155029172584239531==--